PropertyList: Spanish Property MLS

Find properties by description

find_properties_by_description

Read-onlyIdempotent

Match Spanish properties from a free-form description of what the user wants. Best for vague, conditional, or lifestyle-heavy briefs ("3-bed near a good international school, flexible on budget if there's a sea view"). The matcher translates the brief into one to three parallel structured searches across PropertyList's full MLS, then merges and ranks the results. Returns up to 9 listings with match scores and an explanation of how the brief was interpreted (and what couldn't be resolved). Features in the brief are filters too: a private pool, a communal pool, a sea view, a garden, a garage and the like. Commercial premises are matched too (an office, a local, a bar, a warehouse, a traspaso), never mixed with homes.

Works without an API key up to a daily allowance per user (allowance.daily_answers in the result; briefs that find nothing do not count). An API key has its own, larger allowance. When the allowance is used up the call returns an error naming the limit; search_properties stays available for structured queries.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brief`	Yes	Plain-English (or Spanish) description of what the user is looking for. 10-500 chars.
`language`	No		en

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No
`billed`	No
`limits`	No
`summary`	No
`allowance`	No
`properties`	Yes
`unresolved`	No
`interpretation`	No	How the brief was read, one pill per constraint.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 13, 2026
- addedOutput schema / properties / limits
```
Added value: +{
+  "type": [
+    "object",
+    "null"
+  ]
+}
```

Changed2 schema fields changedOct 7, 2026

addedOutput schema / properties / properties / items / properties / photo

Added value: +{
+  "description": "Absolute https URL of the main photo.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / properties / items / properties / url

Added value: +{
+  "description": "Absolute https URL of the listing on PropertyList.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed6 schema fields changedOct 6, 2026

addedOutput schema / properties / allowance

Added value: +{
+  "properties": {
+    "answers_left_today": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "counted_per": {
+      "type": "string"
+    },
+    "daily_answers": {
+      "type": "integer"
+    },
+    "resets": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / interpretation / description

Added value: +"How the brief was read, one pill per constraint."

changedOutput schema / properties / interpretation / type

Previous value: -[
-  "object",
-  "null"
-]New value: +[
+  "array",
+  "null"
+]

addedOutput schema / properties / properties / items / properties / location / description
```
Added value: +"\"Suburb, City\"."
```
changedOutput schema / properties / properties / items / properties / location / type
```
Previous value: -"object"New value: +[
+  "string",
+  "null"
+]
```
changedOutput schema / properties / properties / items / properties / title / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed2 schema fields changedSep 10, 2026

addedOutput schema / properties / billed

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

addedOutput schema / properties / error

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

Changed1 schema field changedAug 23, 2026

changedInput schema / properties / language / enum

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

First observedJul 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent safe-read profile; the description goes far beyond them, disclosing the quota model (daily allowance without a key, larger with a key, briefs that find nothing don't count), the exact failure mode when exhausted, the result cap (up to 9 listings with scores and an interpretation explanation), and that commercial premises are never mixed with homes.

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 and the when-to-use condition before quota mechanics, and nearly every clause carries new information. The parenthetical marketing example and the feature list are slightly padded, but nothing is wasted or buried.

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?

For an open-ended semantic-search tool with an output schema already describing the return payload, the description covers everything the agent needs: invocation form, quota and error behavior, result cap, interpretation feedback, and residential/commercial separation. No material gap remains.

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 50%: 'brief' is documented in the schema, while the 15-value 'language' enum has no description at all and is not addressed in the tool description. The description does compensate well for 'brief' — explaining what a brief can contain, that features like pool/sea view act as filters, and that vague conditional phrasing is supported — but the language parameter remains undocumented.

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 (match) and resource (Spanish properties) from a free-form brief, and names the sibling it contrasts with (search_properties for structured queries). An agent can distinguish it from search_properties and find_similar_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?

'Best for vague, conditional, or lifestyle-heavy briefs' gives clear selection context with an example, and the closing sentence routes structured queries to search_properties. It never states an explicit 'do not use this when...' exclusion, so it falls just short of the top band.

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?