catastro

Consultar inmueble del Catastro espanol

consultar_inmueble_catastro

Read-only

Devuelve datos catastrales no protegidos de un inmueble espanol a partir de su referencia catastral: clase (urbano/rustico), uso principal, superficie construida (m2), anio de construccion, direccion normalizada y desglose de construcciones (urbano) o cultivos (rustico). Traduce el servicio SOAP/XML de la Direccion General del Catastro (OVC) a JSON denso. Acepta referencias de 14/18/20 caracteres; si la de 14 (parcela) resuelve a varios inmuebles, devuelve la lista de candidatos para desambiguar.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`referenciaCatastral`	Yes	Referencia catastral espanola de 14 (parcela), 18 o 20 (inmueble) caracteres alfanumericos. Ejemplo: 9872023VH5797S0001WX

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	Yes
`status`	Yes
`message`	Yes
`property`	Yes
`candidates`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds that it returns non-protected data, translates SOAP/XML to dense JSON, and returns a candidate list for ambiguous 14-character references. This gives useful behavioral detail not captured by annotations.

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?

The description is three sentences of substantive content, front-loaded with the main purpose and output fields. Every sentence adds value, with no repetition of schema details or fluff.

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?

Given the single parameter, existing output schema, and read-only annotations, the description sufficiently covers the tool's purpose, input format, ambiguity behavior, and return content. It is complete for an agent to decide and invoke correctly.

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% with a detailed parameter description including pattern and example. The description adds extra meaning by explaining that 14-character references are parcels and may yield multiple candidates, which is not in the schema.

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?

The description clearly states the tool returns non-protected cadastral data for a Spanish property from its cadastral reference, listing the specific fields returned. The input method (referencia catastral) distinguishes it from sibling tools that use coordinates or address.

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?

The description provides clear context by specifying accepted reference lengths (14/18/20 characters) and explaining the disambiguation behavior for 14-character references that resolve to multiple properties. It does not explicitly exclude alternatives or state 'when not to use', but the input-based purpose is clear.

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

All catastro tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool is uniquely identified by its input method: cadastral reference, coordinates, or address. There is no overlap in purpose; they all return the same normalized data but from different lookup keys, making selection unambiguous.

Naming Consistency4/5

All tools start with 'consultar_inmueble', but the first uses 'catastro' while the others use 'por_coordenadas' and 'por_direccion'. The pattern is almost consistent, with a minor deviation in the first tool.

Tool Count4/5

With 3 tools, the set is slightly lean but appropriate for a focused cadastral lookup service. Each tool covers a distinct and essential query method, so the count feels justified rather than sparse.

Completeness4/5

The tools cover the three primary ways to look up a property (reference, coordinates, address) and return comprehensive property data. Minor gaps exist, such as lack of batch queries or cartographic data, but the core domain is well-covered for typical use cases.

Resources

Need Help?