MapleStats MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_queryA | Plan which sources answer a question that may span several agencies. Use for: the first call on a substantive question ("How have rents and interest rates moved in Calgary since 2020?"). Returns the topics it touches, the tools to call for each in order, local portals for any province or city named, and caveats on combining them. Then run the steps with call_tool. Read-only and offline: it matches the question against this server's source map and calls no external API. Use search_tools instead to find a single tool for a narrow, single-source need. lang='fr' gives the labels, purposes, caveats and guidance in French; tool and argument names stay as they are. Keywords: plan, which data source, where to find, combine sources, cross-source, question, research, Canada data. Mots-clés : planifier, quelle source de données, où trouver, combiner des sources, question, recherche, données canadiennes, statistiques. |
| search_toolsA | Find the right data tool for one specific need by plain-language search. Use for: locating a tool when you know roughly what data you want (a StatCan table, Bank of Canada series, a city's open-data portal). Returns the best-matching tool definitions, ranked by relevance, each with its name, description and full input schema, in the same format as list_tools. Read-only; it searches this server's catalogue only and calls no external API. Use plan_query instead when a question may span several sources or you do not know where to start; use call_tool to run a tool once you have its name. Queries in English or French both work. An empty result means no tool matched: rephrase with topic words (e.g. 'housing starts' rather than 'CMHC table'). |
| call_toolA | Run one data tool found through search_tools or plan_query. Use for: executing a tool by exact name with arguments that match the inputSchema search_tools returned for it. Every reachable tool is read-only: it fetches public data from the upstream agency (StatCan, Bank of Canada, open-data portals) and changes nothing. Returns that tool's typed result, including a provenance block (source, URL, query time, freshness). Errors come back as MCP tool errors, not as data: an unknown or misspelled name raises 'Unknown tool' (search again for the exact name), invalid arguments raise a validation error naming the field, and upstream outages or empty matches raise a typed error explaining what to change. search_tools, call_tool and plan_query cannot be called through it; call them directly. Tool calls are subject to the server's timeout (MAPLE_TOOL_TIMEOUT_SECONDS, default 120). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| compare_boc_series | Guided workflow: fetch several Bank of Canada series together for comparison over the same date range. |
| find_and_fetch_boc_series | Guided workflow: find a Bank of Canada Valet series on a topic and fetch its recent observations. |
| find_and_query_cmhc_table | Guided workflow: find a CMHC HMIP category on a topic and fetch its data. |
| eccc_severe_weather_check | Guided workflow: check for active weather alerts affecting a Canadian location. |
| find_and_query_eccc_collection | Guided workflow: find an MSC GeoMet collection on a topic and query its data. |
| build_sdmx_or_key | Guided workflow: build a complete SDMX OR key for a large dimension. |
| find_and_fetch_series | Guided workflow: find a StatCan series on a topic and fetch its latest data. |
| look_up_classification | Guided workflow: look up a StatCan classification (e.g. NAICS) for a topic. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| module_catalogue_doc | Bilingual (EN/FR) directory of every module this server exposes, by name and description — use this to see what a source covers in French before deciding which tools to call. |
| boc_gotchas_doc | List known Bank of Canada Valet API quirks that are easy to get wrong. |
| boc_well_known_series_doc | List well-known Bank of Canada Valet series/groups for FX, interest rates, CPI/inflation, and commodity prices. |
| cmhc_gotchas_doc | List known CMHC HMIP quirks that are easy to get wrong. |
| cmhc_well_known_categories_doc | List well-known CMHC HMIP categories for rental market, housing starts, seniors housing, and population/household indicators. |
| eccc_gotchas_doc | List known MSC GeoMet-OGC-API quirks that are easy to get wrong. |
| eccc_well_known_collections_doc | List well-known MSC GeoMet collections for alerts, current conditions, AQHI, climate normals/observations, hydrometric, and marine data. |
| statcan_addressing_doc | Explain StatCan's productId/vectorId/coordinate addressing system. |
| statcan_gotchas_doc | List known StatCan API quirks that are easy to get wrong. |
TDQS
Scored across 3 tools
The three tools occupy distinct roles: plan_query for multi-source research planning, search_tools for locating a single tool, call_tool for execution. The descriptions explicitly cross-reference each other with 'use X instead' guidance, though plan_query and search_tools both serve discovery and could occasionally be confused by an agent unsure of question scope.
All three tools follow a clean verb_noun snake_case pattern (plan_query, search_tools, call_tool) with no mixing of conventions or vague verbs. The naming is fully predictable and readable.
Three tools is at the low end but well-matched to a router/meta-layer server whose real data tools are discovered dynamically rather than enumerated as fixed tools. The plan-search-execute trio is coherent and each earns its place, though the surface is minimal.
The meta-lifecycle is covered: planning (plan_query), discovery (search_tools), and execution (call_tool), plus error handling and provenance described. The main gap is no dedicated catalogue-browsing tool, relying on search_tools and the implied list_tools, which could hinder full-surface exploration.