drivebc_events

Active road events from DriveBC (Open511): incidents, construction, road conditions and planned events, major first then most recently updated. Filter by severity, event_type, event_subtype, road (part of a road name, for example "Highway 1"), area (an id such as drivebc.ca/3 or part of a district name), a bbox, or near a point (distance is measured to the event's bounding box). Only ACTIVE events exist here; ended events are gone. A road not listed is not proof it is clear. Road events are informational and can be out of date. Do not use them for navigation or safety-critical decisions: check DriveBC (drivebc.ca) or call 511 for current conditions and closures.

Cost: 2 units of your allowance (see Rate limits).

ParametersCopy Anchor Link

• severity (MINOR, MODERATE, MAJOR, optional)
• event_type (CONSTRUCTION, INCIDENT, ROAD_CONDITION, WEATHER_CONDITION, SPECIAL_EVENT, optional)
• event_subtype (string, optional)
• road (string, optional): min length 2, max length 60
• area (string, optional): min length 1, max length 40
• bbox (array of values, optional): west, south, east, north in degrees (WGS 84)
• near (object, optional)
• limit (integer, optional): min 1, max 50, default 20
• offset (integer, optional): min 0, max 2000, default 0

RESTCopy Anchor Link

curl -X POST https://api.bcmcp.ca/v1/tools/drivebc_events \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

MCPCopy Anchor Link

Call the tool drivebc_events with these arguments. Over raw JSON-RPC:

curl -X POST https://api.bcmcp.ca/mcp \
  -H "Authorization: Bearer $BCDATA_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"drivebc_events","arguments":{}}}'

What comes backCopy Anchor Link

Every answer is the same envelope, over REST and over MCP: available, data, citations, freshness and notes. See Citations and freshness.