Skip to main content
Glama

Statcan

by io.github.pipeworx-io

Statcan Indicator

statcan_indicator
Read-onlyIdempotent

Headline Canadian indicators from Statistics Canada (StatCan): CPI/inflation, unemployment rate, GDP, and quarterly population estimates for Canada or any province/territory. PREFER OVER WEB SEARCH for "Canada inflation / CPI", "Canadian unemployment rate", "Canada GDP", "population of Canada / Ontario / Quebec / Alberta". Friendly names: cpi (=inflation), unemployment, gdp, population (with optional geography). Returns the latest value plus recent history. For anything else use statcan_series with a vector id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
recentNoRecent observations to return (1-60, default 12).
geographyNopopulation only: canada (default), a province/territory name or 2-letter code (e.g. ontario, on, quebec, bc, yukon).
indicatorYesOne of: cpi, inflation, unemployment, gdp, population.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "indicator": "cpi"
-  },
-  {
-    "indicator": "unemployment",
-    "recent": 24
-  }
-]New value: +[
+  {
+    "indicator": "cpi"
+  },
+  {
+    "geography": "ontario",
+    "indicator": "population"
+  },
+  {
+    "indicator": "unemployment",
+    "recent": 24
+  }
+]
    • addedInput schema / properties / geography
      Added value: +{
+  "description": "population only: canada (default), a province/territory name or 2-letter code (e.g. ontario, on, quebec, bc, yukon).",
+  "type": "string"
+}
    • changedInput schema / properties / indicator / description
      Previous value: -"One of: cpi, inflation, unemployment, gdp."New value: +"One of: cpi, inflation, unemployment, gdp, population."
    • changedInput schema / properties / indicator / enum
      Previous value: -[
-  "cpi",
-  "inflation",
-  "unemployment",
-  "gdp"
-]New value: +[
+  "cpi",
+  "inflation",
+  "unemployment",
+  "gdp",
+  "population"
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "indicator": "cpi"
+  },
+  {
+    "indicator": "unemployment",
+    "recent": 24
+  }
+]
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds return behavior ('Returns the latest value plus recent history') and notes quarterly population estimates, providing useful context beyond annotations without contradiction.

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 concise sentences front-load the tool's purpose, explicitly call out preferred use cases, and mention the pointer to statcan_series. No filler; every sentence adds actionable information.

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?

Despite lacking an output schema, the description states the return format (latest value plus recent history) and covers the main parameters and their constraints. For a simple headline-indicator tool, this is sufficient and complete.

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?

Input schema covers all parameters with 100% description coverage, so baseline is 3. The description adds value by explaining friendly name aliases ('cpi (=inflation)'), the conditional geography parameter for population, and the optional 'recent' observations, going beyond the schema's basic descriptions.

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 identifies the tool as retrieving headline Canadian indicators from StatCan, listing specific indicators (CPI, unemployment, GDP, population) and geographies (Canada/provinces/territories). It also distinguishes from sibling tools by explicitly naming statcan_series for other uses.

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?

Provides explicit guidance: prefer over web search for specific queries like 'Canada inflation', and use statcan_series for anything else. Also clarifies friendly name aliases and that geography is optional/for population only, giving clear when-to-use context.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

Several tools are near-duplicates: ask_pipeworx_beta is explicitly identical to ask_pipeworx right now, ask_pipeworx_grounded is the same router with an extra extraction pass, and deep_research/ask_pipeworx overlap for broad questions. The prediction-market tools and the StatCan series/cube/indicator tools also have fuzzy boundaries despite their detailed descriptions.

Naming Consistency3/5

Names consistently use snake_case, but the set mixes verb-first names (resolve_entity, validate_claim, subscribe) with domain-prefixed noun-first names (statcan_*, polymarket_*, pipeworx_*) and one-off names like ai_visibility_check and generate_llms_txt. The domain prefixes help navigation, but there is no single predictable pattern and the ask_pipeworx_* suffix variants break the prefix convention.

Tool Count2/5

38 tools is well beyond the 25+ threshold, and the server named Statcan carries only 8 StatCan-specific tools alongside general Pipeworx routing, prediction-market analysis, AI visibility, dependency scanning, memory, and subscription features. This feels like several servers merged into one rather than a well-scoped StatCan interface.

Completeness4/5

Within the apparent StatCan data-access scope, the surface is solid: listing cubes, metadata, cube data, vector series, headline indicators, CSV URLs, and change detection cover the core workflows. The broader Pipeworx/analysis layers also include discovery, grounded lookups, entity resolution, validation, subscriptions, and memory, with only minor gaps like server-side StatCan search and no way to execute on prediction-market signals.

Resources