Spain Open Data MCP

Resolve a Spanish place

resolve_place

Read-onlyIdempotent

Convert Spanish place names into official INE codes and levels (region, province, municipality, district, tract) before querying statistics. Handles accents and local names.

Instructions

Find the INE code and level (CCAA, province, municipality, district, tract) for a place in Spain.

Use this first when a question names a place. Returns the best match first, with
alternatives (e.g. 'Valencia' is both a city and a province). Handles accents, Basque,
Catalan and Galician names, and common English names (Seville, Catalonia).
Neighbourhood names are not supported; use districts or tracts from `demographics`
or `income` with `sub_areas`.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	Place name or INE code, e.g. 'A Coruña', 'Mérida, Badajoz', '08'.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`checks`	No
`sources`	Yes
`confidence`	Yes	Lowest confidence across inputs: high, medium or low. Never state a conclusion more strongly than this.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so extra credit goes to the description's added behavior: best match returned first with alternatives for ambiguous names, multilingual/accents handling, and the neighbourhood limitation. Return format is delegated to the existing output schema, so 4 rather than 5.

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?

Front-loaded with the outcome, followed by the highest-priority usage rule, then edge cases. Every sentence carries distinct information with no padding.

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?

For a single-parameter read tool with full schema coverage, complete annotations, and an output schema, the description covers ambiguity, scope limits, and language handling. Nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the param description already documents that 'query' accepts a place name or an INE code with examples. The description reinforces ambiguity handling ('Valencia' is both city and province) but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (find/resolve) and resource (INE code and level for a Spanish place), and enumerates the exact levels returned (CCAA, province, municipality, district, tract). An agent can distinguish it from the sibling data tools without opening a schema.

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?

Explicitly says 'Use this first when a question names a place', and routes unsupported work elsewhere: 'Neighbourhood names are not supported; use districts or tracts from `demographics` or `income` with `sub_areas`.' This names both when-to-use and when-not with a concrete alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server