Spain Open Data

Resolve a Spanish place

resolve_place

Read-onlyIdempotent

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). Districts and tracts are shown with the OpenStreetMap neighbourhood names inside them ('Valladolid distrito 10 (Parquesol, Girón, La Victoria)'), and a neighbourhood name ('Parquesol, Valladolid', 'Gràcia, Barcelona') returns the INE district that contains it.

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.

Changed4 schema fields changedOct 17, 2026

addedOutput schema / $defs / Place / properties / area_names

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "For districts and tracts: OpenStreetMap neighbourhood names inside it (not official INE names).",
+  "title": "Area Names"
+}

changedOutput schema / $defs / Place / properties / match / description

Previous value: -"How the query matched. 'fuzzy' means a spelling guess: confirm it."New value: +"How the query matched. 'fuzzy' means a spelling guess: confirm it. 'neighbourhood' means a neighbourhood name was found inside this INE district."

changedOutput schema / $defs / Place / properties / match / enum

Previous value: -[
-  "code",
-  "exact",
-  "prefix",
-  "fuzzy"
-]New value: +[
+  "code",
+  "exact",
+  "prefix",
+  "fuzzy",
+  "neighbourhood"
+]

addedOutput schema / $defs / Place / properties / matched_name

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "The neighbourhood name that matched, if any.",
+  "title": "Matched Name"
+}

First observedOct 17, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds substantial behavior beyond them: best-match-first ordering with alternatives returned, multilingual/accents handling, and the non-obvious district/tract neighbourhood-name mapping in both directions. This is exactly the extra context an agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the purpose and the 'use first' directive, then uses the remaining lines for genuinely load-bearing detail on matching and neighbourhood resolution. Slightly long with the parenthetical examples, but every clause carries information.

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?

An output schema exists, so return shape needn't be spelled out, yet the description still explains return semantics (best match first, alternatives follow). Combined with annotations and full schema coverage, an agent has everything needed to invoke and interpret this tool.

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

Parameters4/5

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

Schema coverage is 100% and the single param is already described, so baseline is 3. The description adds real meaning beyond the schema: that the query accepts INE codes, multilingual/English place names, and neighbourhood names ('Parquesol, Valladolid') that resolve to a containing district.

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+resource (resolve a Spanish place to its INE code and level) and enumerates the level taxonomy (CCAA, province, municipality, district, tract). No sibling tool overlaps with place resolution, so an agent can immediately route here for geographic grounding.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/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,' which gives clear priority ordering relative to the sibling dataset tools (income, crime, demographics, etc.) that all need a place code. It does not name a specific alternative or state when-not-to-use, so it falls just short of a 5.

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

All Spain Open Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.