Spain Open Data MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPAIN_MCP_OFFLINE | No | `1` serves only from cache (tests, evals) | |
| SPAIN_MCP_CACHE_DIR | No | On-disk cache of upstream responses | ~/.cache/spain-open-data-mcp |
| SPAIN_MCP_HTTP_TIMEOUT | No | Seconds per upstream request | 60 |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve_placeA | Find the INE code and level (CCAA, province, municipality, district, tract) for a place in Spain. |
| demographicsA | Population, sex, five-year age bands, 5-year trend, and household profile for a place in Spain. |
| incomeA | Household income for a place in Spain from INE's income atlas, down to census tract. Returns net and gross income per person and per household, mean and median per consumption unit, inequality (Gini, P80/P20), income sources (wages, pensions, benefits), a trend, and benchmarks against the province, region and Spain. Use it for purchasing power, price positioning and choosing between districts. Figures are euros of the data year; the atlas runs about two years behind. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| data-licences | Where each figure comes from, its licence and the attribution it requires. |
TDQS
Scored across 3 tools
Each tool targets a clearly distinct concern: resolve_place does code/level lookup, demographics returns population/household data, and income returns economic data. Descriptions explicitly explain when to use each and how they chain, leaving little room for misselection.
Names mix conventions: resolve_place is a verb_noun pattern while demographics and income are bare nouns. It is still readable and each name is self-explanatory, but there is no single predictable pattern.
Three tools is on the thin side for a server branded as covering Spanish open data broadly, though it is coherent for a focused socioeconomic surface. Each tool earns its place but the set feels lean.
The resolve_place → demographics/income chain gives a complete workflow for place-based socioeconomic queries, with sub_areas supporting drill-down. Gaps exist for other open-data domains (housing, employment, health), but the stated socioeconomic purpose is well covered.