Statistics Canada MCP Server

get_changed_series_data_from_vector

Retrieve only the data points that have changed for a Statistics Canada series using its Vector ID, enabling efficient tracking of updates.

Instructions

Get changed series data (data points that have changed) for a series identified by Vector ID. Disables SSL Verification. Corresponds to: POST /getChangedSeriesDataFromVector

Returns: Dict[str, Any]: A dictionary containing the changed series data object. Raises: httpx.HTTPStatusError: If the API returns an error status code. ValueError: If the API response format is unexpected or status is not SUCCESS. Exception: For other network or unexpected errors.

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vectorId": "<vectorId>"
    },
    "name": "get_changed_series_data_from_vector"
  }
}

Input Schema

Name	Required	Description	Default
`vectorId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.15Aug 6, 2026

TDQS

B3.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behaviors: it 'Disables SSL Verification,' notes the HTTP endpoint, specifies return type, and lists possible exceptions. It also includes an important instruction about citing the VectorId, which is useful context beyond basic functionality.

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

Conciseness4/5

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

The description is well-structured with sections for purpose, endpoint, returns, raises, and an important note. It is slightly verbose but each sentence serves a purpose, though the phrase 'data points that have changed' is redundant with the tool name.

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?

For a tool with one parameter, no annotations, and no output schema, the description covers purpose, security behavior, endpoint, return type, exceptions, and a usage instruction. It lacks parameter semantics and detailed return structure, but overall provides a solid context for invocation.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not explain the 'vectorId' parameter beyond its name. It repeats 'Vector ID' without providing details on format, range, or how to obtain it, adding no semantic value over the schema.

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 'Get changed series data (data points that have changed) for a series identified by Vector ID,' specifying a distinct verb, resource, and identifier. It differentiates from siblings like get_changed_series_data_from_cube_pid_coord, which uses a different identification method.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor mentions any sibling tools or exclusions. It only describes the operation itself, leaving the agent to infer applicability from the name.

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