statsmapped-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport mode for the MCP server. Set to 'streamable-http' to enable hosted HTTP mode; default is stdio. | stdio |
| STATSMAPPED_MCP_BASE_URL | No | Base URL of the StatsMapped public API. Override for testing or alternate endpoints. | https://statsmapped.com |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_datasetsA | List every dataset (stat) StatsMapped tracks for one country ('ireland'
or 'united-kingdom'), with its key, human label, and which geography levels
it can be shown at. Ireland and the UK track genuinely different datasets --
call this for the right country before assuming a stat_key exists there.
Call this first to find the right |
| list_areasA | List every geography at one boundary level, for one country ('ireland'
or 'united-kingdom'). |
| list_area_datasetsA | List every dataset available for one area (e.g. "county:kerry" for
Ireland, "uk:lad:e09000033" for the UK), with its latest figure, year-on-
year change, and caveat labels only (not full caveat text -- call
|
| get_dataset_for_areaA | Full detail for one dataset in one area: the latest figure, a written
summary, full caveat text, and (if |
| rank_areasA | Rank every area at one geography level by its latest figure for one stat,
for one country -- e.g. "which counties have the highest median sale price"
(country="ireland") or "which local authorities award the most single-bid
contracts" (country="united-kingdom"). Where the underlying stat has no honest per-area denominator (crime,
homelessness, live_register and similar -- StatsMapped's own
RANKING_NO_DENOMINATOR_STATS), each row's |
| list_comparisonsA | List every registered cross-dataset comparison pair for one country
('ireland' or 'united-kingdom') -- e.g. "median sale price vs new dwelling
completions per 1,000 residents". A small, hand-curated set, not an
arbitrary-pair engine: pass one of the returned |
| get_comparisonA | Full detail for one registered comparison pair: each axis's label, unit
and publisher, the correlation stats (r, rho, and a leave-one-out
sensitivity range naming the single most influential area), and caveats.
|
| check_comparabilityA | Does StatsMapped have a registered, hand-vetted comparison between these
two stats ('ireland' or 'united-kingdom')? Registry-backed only -- never
computes a fresh correlation for an arbitrary pair. Both stat_keys come from
|
| explain_metricA | Definition, methodology and standing caveats for ONE stat ('ireland' or
'united-kingdom') -- never a current figure. Call this when the question is
about what a metric MEANS or how it's measured ("how is the claimant count
defined", "is this a mean or a median"), not about a specific area's value --
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool targets a distinct resource/action: global dataset listing, area listing, per-area dataset listing, detailed dataset retrieval, ranking, comparison listing, comparison details, comparability check, and metric explanation. The descriptions explicitly call out differences (e.g., stat_key vs series_key, list_datasets vs list_area_datasets), eliminating ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: list_datasets, list_areas, list_area_datasets, get_dataset_for_area, rank_areas, list_comparisons, get_comparison, check_comparability, explain_metric. No mixed conventions or vague verbs.
9 tools is well within the ideal 3-15 range. Each tool serves a distinct purpose in the domain of querying Irish/UK statistical data, and none feel redundant or unnecessary.
The tool set covers the full lifecycle of data exploration: discovery (list_datasets, list_areas, list_area_datasets, list_comparisons), retrieval (get_dataset_for_area, get_comparison), ranking, comparability checking, and metric explanation. There are no obvious gaps; even history and caveats are handled.