Skip to main content
Glama
Sign In

Statcan

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Statcan Csv Url

statcan_csv_url
Read-onlyIdempotent

Return the StatCan-hosted URL for a full cube as a CSV download (doesn't fetch the file — hands back a direct URL).

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_csv_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoen | fr (default en).
product_idYesCube product ID.

Output Schema

NameRequiredDescriptionDefault
statusYesResponse status from API
languageYesLanguage code
product_idYesCube product ID
download_urlYesStatCan-hosted CSV download URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds behavioral context by stating it returns a URL and does not fetch the file, which is consistent and provides useful additional detail.

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?

The description is a single, well-structured sentence with no redundant information. Every word serves a purpose.

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

Completeness4/5

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

Given the simple nature of the tool (returning a URL), and the presence of a likely output schema, the description is sufficiently complete. It could mention error handling or conditions, but not necessary for basic operation.

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?

Schema coverage is 100%, so baseline is 3. The description adds slight value by mentioning 'full cube' implying the URL is for the entire cube, but does not elaborate on parameter specifics beyond what the schema already provides.

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?

The description clearly states the verb 'Return' and the resource 'StatCan-hosted URL for a full cube as a CSV download'. It explicitly distinguishes from likely siblings that fetch data by stating 'doesn't fetch the file — hands back a direct URL'.

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

Usage Guidelines3/5

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

The description implies when to use it (when you need the URL without downloading), but does not explicitly mention when not to use it or compare to alternatives like statcan_cube_data.

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

All Statcan toolsInspect
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.

Resources