drivebc_event

One active road event by id, with the point or line it covers (at most 200 points; a longer line is sampled, keeping both ends). The event must be in the current active set: an id that is not there is reported as not active, never guessed. 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: 3 units of your allowance (see Rate limits).

ParametersCopy Anchor Link

• id (string, required)

RESTCopy Anchor Link

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

MCPCopy Anchor Link

Call the tool drivebc_event 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_event","arguments":{"id":"..."}}}'

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.