BC Data docs

catalogue_dataset

One catalogue dataset

The stored metadata for one dataset by its name (the slug in the catalogue address) or id: description, publisher, licence and what it allows, tags, and the resources (name, format, update cycle, and a link only when the licence is open).

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

Parameters

  • name (string, required): min length 1, max length 200

REST

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

MCP

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

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