Skip to main content
Glama
Sign In

Statcan

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Statcan Changed Series

statcan_changed_series
Read-onlyIdempotent

List StatCan series that changed (new release) on a given date (default today). Useful to detect updated cubes for scheduled refreshes.

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": {},
    "name": "statcan_changed_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD (default today).

Output Schema

NameRequiredDescriptionDefault
dateYesQuery date (YYYY-MM-DD or 'today')
countYesNumber of changed series
seriesYesList of changed series

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, which cover safety and side effects. The description adds minimal behavioral context beyond the annotation, so burden is shifted to 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 description is concise: two sentences with no wasted words. The purpose is front-loaded and immediately understandable.

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?

The tool is simple with one optional parameter and an output schema present. The description adequately covers purpose and usage. Could potentially mention return type but assumed from 'list'.

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%, and the description does not add additional meaning beyond what the schema's parameter description provides ('YYYY-MM-DD (default today)'). Baseline 3 is appropriate.

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 action (list), the resource (StatCan series that changed), and the context (on a given date). It distinguishes itself from sibling tools like statcan_series by specifying 'changed' series for new releases.

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

Usage Guidelines4/5

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

Explicitly states a use case: 'detect updated cubes for scheduled refreshes.' While it doesn't provide when-not-to-use or alternatives, the context is clear for a simple listing tool.

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