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. lang is accepted for consistency; the plan text is English. 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 | Search for tools using natural language. Returns matching tool definitions ranked by relevance, in the same format as list_tools. |
| call_toolB | Call a tool by name with the given arguments. Use this to execute tools discovered via search_tools. |
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 have distinct primary purposes: plan_query orchestrates multi-source questions, search_tools discovers tools, and call_tool executes them. However, plan_query also returns tools to call, which could overlap with search_tools for simple discovery, creating minor ambiguity.
All names use snake_case and follow a consistent verb_noun pattern (call_tool, search_tools, plan_query), making them predictable and readable.
With only 3 tools, the server is minimal but appropriate for a meta-orchestration layer; each tool (plan, search, call) is essential to the workflow, and no tool feels redundant.
The surface covers the core lifecycle of planning, discovering, and executing tools. A direct 'list all tools' operation is missing, but search_tools with a broad query can substitute, so there's no hard dead end.