ferry_routes

B.C. coastal ferry routes from the province's Coastal Ferry Routes layer on DataBC, read live: route name, what it carries (the layer's own values: all, passenger, passenger and freight, freight, freight and vehicle), operator, a usage band (very low to very high, or unknown), length in km and where the line was drawn from. Filter by name or operator. Geography only: NOT schedules, fares, sailings or live status, and the lines are approximate.

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

ParametersCopy Anchor Link

• name (string, optional): min length 1, max length 60
• operator (string, optional): min length 1, max length 60
• limit (integer, optional): min 1, max 50, default 25

RESTCopy Anchor Link

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

MCPCopy Anchor Link

Call the tool ferry_routes 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":"ferry_routes","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.