PropertyList: Spanish Property MLS

Verified valuation

verified_valuation

Read-onlyIdempotent

Get a valuation for a property or area from recorded market data, not asking prices. Returns the €/m² for the municipality and segment, an indicative valuation when you give a size (build_sqm) or a listing reference, and a content-hashed attestation URL the figure can be cited from.

Check verified before citing. It is true ONLY for Spanish figures drawn from the notarial register (Consejo General del Notariado) with at least 10 recorded transactions behind them. Elsewhere - Portugal and Cyprus especially - the figure comes from a national house-price index and is an estimate: transaction_backed is false, source_label names the real source, and it must not be described as notary-verified. indicative_band_pct widens as the evidence thins.

Transactions are recorded per municipality, so a query for a sub-area (Sotogrande, Puerto Banus, Nueva Andalucia, Orihuela Costa) is answered with the containing municipality's attestation: rolled_up_from_sub_area is true, location and municipality_code name the municipality, requested_area is what you asked for and rollup_note is the sentence to repeat. Never quote a rolled-up figure as the sub-area's own price.

Only two segment attestations exist per municipality, so a request for penthouse or townhouse resolves to the nearest attested segment. property_type is the segment actually used and requested_property_type is what you asked for; when they differ the text says so. Also returns our proprietary network achieved-sale figure where available. If no attestation covers the area yet, it says so plainly (use area_market_summary for asking-price stats instead).

Input Schema

TableJSON Schema

Name	Required	Description
`build`	No	Alias of build_sqm.
`location`	No	Municipality / city name, e.g. "Marbella". Ignored if a reference is given.
`build_sqm`	No	Built size in m² to value. Optional.
`reference`	No	Value a specific PropertyList listing by reference (uses its municipality, type and size). Optional.
`build_size`	No	Alias of build_sqm.
`property_type`	No	Optional segment slug: apartment, villa, penthouse, townhouse, plot. Defaults to the municipality-wide figure.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`source`	No
`network`	No
`location`	Yes
`on_chain`	No
`verified`	Yes
`build_sqm`	No
`period_end`	No
`rollup_note`	No
`sample_size`	No
`content_hash`	No
`source_label`	No
`property_type`	No
`requested_area`	No
`attestation_url`	No
`indicative_range`	No
`municipality_code`	No
`transaction_backed`	No
`valuation_estimate`	No
`indicative_band_pct`	No
`verified_price_per_sqm`	No
`requested_property_type`	No
`rolled_up_from_sub_area`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / municipality_code

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / requested_area

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / rolled_up_from_sub_area
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / rollup_note

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed2 schema fields changedAug 19, 2026

addedInput schema / properties / build

Added value: +{
+  "description": "Alias of build_sqm.",
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / build_size

Added value: +{
+  "description": "Alias of build_sqm.",
+  "minimum": 1,
+  "type": "integer"
+}

Changed4 schema fields changedAug 4, 2026
- addedOutput schema / properties / indicative_band_pct
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / requested_property_type
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / source_label
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / transaction_backed
```
Added value: +{
+  "type": "boolean"
+}
```
First observedJul 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds rich behavioral context beyond the readOnly/idempotent annotations: the meaning of 'verified', the distinction between notarial and index-based sources, the rollup behavior for sub-areas, the segment fallback, and the field-level caveats. It clearly explains what users must check before citing the result. This is far more than the annotations alone provide.

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?

The description is long but organized in clear thematic paragraphs and front-loads the core purpose. Every paragraph carries an actionable caveat, and the density is justified by the tool's complexity. It is not minimal, but it avoids redundancy and each sentence earns its place.

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?

The description covers all essential aspects of the tool: data source, verification semantics, geographic aggregation, segment fallback, alternative tool, and error/fallback behavior. Given the rich output schema and read-only annotations, nothing an agent needs to call the tool correctly or interpret its results is missing.

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%, so the baseline is a 3, but the description adds meaning beyond the schema by explaining how parameters affect the result: build_sqm produces an indicative valuation, reference values a listing, property_type resolves to the nearest attested segment, and sub-area locations roll up to the containing municipality. These behavioral details are not inferable from the schema alone.

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 opens with a specific verb and resource: 'Get a valuation for a property or area from recorded market data, not asking prices.' It clearly distinguishes itself from the sibling area_market_summary by noting that asking-price statistics belong to that tool. The tool's scope and output are stated explicitly.

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?

The description explains when the tool is appropriate ('recorded market data, not asking prices') and gives an explicit alternative: 'use area_market_summary for asking-price stats instead.' It also warns against quoting rolled-up or unverified figures, giving concrete conditions for when the data can and cannot be used.

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

All PropertyList: Spanish Property MLS 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.

Resources

Need Help?