BC Data docs

drivebc_status

DriveBC source: availability and areas

Whether the DriveBC proxy is on, when it was last read successfully, the last upstream error, the cache and staleness rules, and the 11 DriveBC areas usable as the area filter. Use it to tell 'no events' from 'source unreachable'.

Cost: 1 unit of your allowance (see Rate limits).

Parameters

This tool takes no arguments. Send {}.

REST

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

MCP

Call the tool drivebc_status 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_status","arguments":{}}}'

What comes back

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

On this page