Statcan

Statcan Cube Metadata

statcan_cube_metadata

Read-onlyIdempotent

Full metadata for a StatCan cube: dimensions, member trees, frequency, geography, last release. Use it to construct a coordinate string for statcan_cube_data. Does NOT return vector IDs — for that use statcan_cube_vectors, which enumerates the actual vector id for every dimension-member combination in the cube.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_id": 36100434
    },
    "name": "statcan_cube_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`product_id`	Yes	Cube product ID (8-digit, e.g. 36100434 = quarterly GDP).

Output Schema

Name	Required	Description
`end_date`	Yes	Cube end date
`title_en`	Yes	English cube title
`title_fr`	Yes	French cube title
`cansim_id`	Yes	CANSIM identifier
`dimensions`	Yes	Cube dimensions
`product_id`	Yes	Cube product ID
`start_date`	Yes	Cube start date
`series_count`	Yes	Total series in cube
`archive_status`	Yes	Archive status in English
`frequency_code`	Yes	Release frequency code
`datapoint_count`	Yes	Total datapoints in cube

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 15, 2026
- changedOutput schema / properties / product_id / type
```
Previous value: -"number"New value: +[
+  "number",
+  "string"
+]
```
AddedJun 20, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description's real contribution is negative-space disclosure — what the tool will NOT return (vector IDs). It doesn't add auth, rate-limit, or caching behavior, but an output schema exists so return shape needn't be restated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the return payload, then the use case, then the boundary. Every clause carries information — no filler, no restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-param read tool with full annotation coverage and an output schema, the description covers everything an agent needs: what comes back, what to do with it, and which sibling to use when this tool is the wrong choice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only one parameter and schema description coverage is 100%, with the schema already giving the 8-digit format and the quarterly-GDP example. The description adds no further constraint, validation rule, or failure mode for product_id, so this sits at the baseline for a fully documented single param.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (a StatCan cube's metadata) and enumerates the contents — dimensions, member trees, frequency, geography, last release — so the agent knows exactly what it gets. It explicitly contrasts itself with statcan_cube_vectors, making sibling disambiguation possible without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete downstream use case ('use it to construct a coordinate string for statcan_cube_data') and an explicit exclusion with the named alternative ('Does NOT return vector IDs — for that use statcan_cube_vectors'). Both the when and the when-not are stated, not inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Statcan tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.