PropertyList: Spanish Property MLS

Get property details

get_property

Read-onlyIdempotent

Fetch the full record for one PropertyList listing by its reference code (the human-readable id like 'PLE-12345'). Use this once the user has settled on a listing from search_properties or find_properties_by_description and wants details or photos. To contact the listing agency, use submit_enquiry - direct phone or email details are not part of the payload.

Works without an API key up to a daily per-IP allowance of distinct listings; an API key raises that allowance.

location.city is whatever tier the listing was filed under and may be a municipality OR a locality inside one. To place a listing administratively use location.municipality (with its INE municipality_code); it is null, never guessed, when we cannot resolve it.

location.latitude / location.longitude are present only when we hold a real, publishable coordinate; the fields are absent otherwise, and are never 0,0. location.coordinates_precision says what the point is: exact or street is the property itself, locality or administrative_area is an area centroid (accurate to the town, not the building), unknown is a pin we hold no precision record for.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`language`	No		en
`reference`	Yes	PropertyList reference, e.g. 'PLE-12345'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`property`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 23, 2026

changedInput schema / properties / language / enum

Previous value: -[
-  "en",
-  "es",
-  "de",
-  "fr",
-  "it",
-  "nl",
-  "pt",
-  "bg",
-  "el",
-  "da",
-  "sv",
-  "no",
-  "fi"
-]New value: +[
+  "en",
+  "es",
+  "de",
+  "fr",
+  "it",
+  "nl",
+  "pt",
+  "bg",
+  "el",
+  "da",
+  "sv",
+  "no",
+  "fi",
+  "pl",
+  "ru"
+]

addedOutput schema / properties / property / properties / features_language
```
Added value: +{
+  "type": "string"
+}
```

First observedJul 27, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations provide readOnly/idempotent hint, but the description adds meaningful behavioral detail: works without an API key up to a daily per-IP allowance and is raised with a key. It also explains tricky response semantics: `city` is the filing tier, `municipality` is never guessed, and coordinates are absent rather than 0,0 when unavailable. No annotation contradiction.

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?

All sentences add value: purpose, sibling alternative, API-key behavior, then two dense field-semantics caveats. Front-loaded; no filler.

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?

Despite no output schema, the description flags the non-obvious fields an agent would otherwise misread (municipality null semantics, latitude/longitude absent, precision tiers) and the authentication/rate-limit context. Enough to call correctly.

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?

reference is described in schema; description reinforces with example. The language parameter receives no description beyond enum names + default. With 50% schema coverage, the description does not fill the gap, but language as an enum of locale codes is low-risk. Score 3.

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 and object: 'Fetch the full record for one PropertyList listing by its reference code.' It precisely identifies the input ('human-readable id like 'PLE-12345''), distinguishes this from search tools by saying it is used after the user has settled on a listing, and names sibling `submit_enquiry` as the alternative for contact details. Clear and unambiguous.

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 when to use: once the user has settled on a listing from search_properties or find_properties_by_description and wants details/photos. It also routes the contact case to submit_enquiryable and notes the API-key/rate-limit context, giving the agent enough to choose between siblings.

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?