Skip to main content
Glama

Statistics Canada MCP Server

by io.github.Aryan-Jhaveri
OverviewDiscussionsAdmin

get_changed_series_list

Read-only

Get the list of series (vectorId, productId, coordinate, releaseTime) updated today. Statistics Canada publishes this list after 08:30 ET; the endpoint does not accept a date. For a historical release date, use get_changed_cube_list(date) to list the cubes updated on that date. Disables SSL Verification. Corresponds to: GET /getChangedSeriesList

Returns: List[Dict[str, Any]]: A list of dictionaries describing changed series objects. Raises: Exception: If the API returns an unexpected status code or network error. ValueError: If today's list has not been released or the response format is unexpected.

IMPORTANT: In your final response to the user, you MUST cite the source of your data. For changed series, this means including the VectorId.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / date
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "date"
-]New value: +[]
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds several non-obvious behaviors: SSL verification is disabled, the endpoint accepts no date, publication happens after 08:30 ET, and specific exceptions occur if the list is unreleased or the response is malformed. It does not contradict the annotations.

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 purpose and usage constraints are front-loaded, and the remaining lines cover return shape and exceptions that are valuable because there is no output schema. The description is appropriately detailed for the tool's operational constraints and contains no obvious filler.

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?

Given the absence of an output schema, the description fully explains the return shape, error conditions, publication timing, SSL behavior, and the historical alternative. An agent has enough information to invoke it correctly and route historical requests elsewhere.

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

Parameters4/5

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

The input schema has zero parameters, so the baseline is 4. The description usefully clarifies that the endpoint does not accept a date, which explains the absence of parameters, but there are no parameter names or formats to further document.

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 states a specific verb and resource: it retrieves the list of series updated today, with the key fields vectorId, productId, coordinate, and releaseTime. It also distinguishes this tool from get_changed_cube_list by noting that the sibling handles historical dates.

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?

It explicitly says when to use this tool: for today's changed series list, after the 08:30 ET publication time. It also says when not to use it for historical dates and directs the agent to get_changed_cube_list(date) instead.

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

All Statistics Canada MCP Server 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