PropertyList: Spanish Property MLS

Find similar properties

find_similar_properties

Read-onlyIdempotent

Listings similar to one property: same market (sale or rent), same town, same kind of home, a similar number of bedrooms and a price within about 25%. Closest in price first. Use it for "show me alternatives to PL12345" or "anything like this but cheaper?".

Every property carries oracle_verified and oracle_attestation_url, as in search_properties.

Input Schema

Name	Required	Description	Default
`limit`	No
`language`	No	Language for titles and description excerpts.	en
`reference`	Yes	Reference of the listing to find alternatives to, e.g. PL12345.

Output Schema

Name	Required	Description	Default
`error`	No
`limits`	No
`reference`	Yes
`properties`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedOutput schema / properties / properties / items / properties / buildable_sqm
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```

Changed2 schema fields changedOct 13, 2026

addedOutput schema / properties / error

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

addedOutput schema / properties / limits

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

AddedOct 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent safety, and the description adds genuinely new behavior: the ~25% price tolerance, the matching dimensions, the 'closest in price first' ordering, and the presence of oracle_verified/oracle_attestation_url on results. It does not discuss result-count behavior or what happens when few matches exist, which is the main remaining gap.

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 core similarity rule and ranking are front-loaded in one dense sentence, followed by usage examples and a short note on result fields. No filler, though the trailing oracle paragraph is a slight afterthought that could be tighter.

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?

With an output schema present, return shape need not be explained, yet the description still flags the oracle fields. The matching heuristic is exactly what an agent needs to interpret why certain listings appear, and only the limit default/cap is left implicit.

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?

Schema coverage is 67%: reference and language are documented in the schema, but limit is undocumented in both places. The description's matching criteria describe filtering behavior, not the parameters, so it adds no meaning about limit or language. Baseline 3 for mid coverage is appropriate.

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 resource ('listings similar to one property') and enumerates the similarity axes — market, town, property type, bedrooms, price band. An agent can distinguish this from search_properties without opening either schema.

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?

Provides two concrete trigger phrases ('show me alternatives to PL12345', 'anything like this but cheaper?') that map directly to intent. It stops short of explicitly naming search_properties as the alternative or stating when not to use this tool, so it falls 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 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?