fetch_record

The stored record for a search hit. With upstream true it also fetches the record's own fetch_url from the source (allow-listed hosts only, size capped) and returns that text, which costs more and counts against a daily budget.

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

ParametersCopy Anchor Link

• ref (string, required): min length 1, max length 120
• upstream (boolean, optional): default false

RESTCopy Anchor Link

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

MCPCopy Anchor Link

Call the tool fetch_record 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":"fetch_record","arguments":{"ref":"..."}}}'

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.