Spain Open Data

Rents

rents

Read-onlyIdempotent

How housing rents have changed in a place: INE's rent index (IPVA, 2015 = 100) with the change over the last year, five years and since 2015, against province, region and Spain.

Covers municipalities over 10,000 residents, districts of provincial capitals, provinces and
regions (not the Basque Country or Navarra). Gives changes, not rents in euros.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`place`	Yes	Place name or INE code: municipality ('Valladolid' or '47186'), province ('41'; a bare name like 'Sevilla' means the city), autonomous community ('Cataluña' or 'CA09'), district ('4718603') or census tract ('4718603012'). 'Name, Province' picks between same-named towns.

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

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral context: the index construction (IPVA, 2015=100), that results are relative changes rather than euro amounts, and the hard coverage exclusions (Basque Country and Navarra).

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-loaded with the core purpose, then the supporting geographies and caveats in short sentences. The three-line layout is efficient, though the coverage list is slightly list-heavy and the exclusions could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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-format explanation is not needed, and the description covers scope, measurement basis and coverage limits. The only gap is that it doesn't hint at using resolve_place when a bare place name is ambiguous, a step the sibling list suggests is available.

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?

With 1 parameter at 100% schema description coverage, the schema already documents accepted formats exhaustively (municipality name/code, province code, community code, district, census tract, and 'Name, Province' disambiguation). The description only restates the entity types covered, adding no syntax 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 resource (INE IPVA rent index, 2015=100) and exactly what the output measures: change over 1 year, 5 years and since 2015, compared against province, region and Spain. It also draws a sharp boundary ('gives changes, not rents in euros'), which separates it from euro-denominated siblings such as price_band or income.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the tool for rent-trend questions. The geographic eligibility rules (municipalities >10,000 residents, districts of provincial capitals, provinces, regions) function as practical use constraints, but there is no explicit when-to-use-vs-alternative guidance and no reference to resolve_place for ambiguous names.

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.