PropertyList: Spanish Property MLS

List agencies

list_agencies

Read-onlyIdempotent

Find PropertyList agencies (estate agents) in a given area, ranked by how many active listings they carry there. Returns up to 10 agencies with name, location, listing count, and url: the agency's page on PropertyList, listing its properties, in the language asked for. url is null for the few agencies PropertyList shows no page for. Use this after a buyer has narrowed in on an area and wants to know which agencies dominate it.

Input Schema

Name	Required	Description	Default
`limit`	No
`language`	No	Language of the agency pages linked in url.	en
`location`	Yes	Place name (city, suburb, or urbanisation). e.g. 'Estepona'.

Output Schema

Name	Required	Description	Default
`agencies`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 30, 2026

addedInput schema / properties / language

Added value: +{
+  "default": "en",
+  "description": "Language of the agency pages linked in url.",
+  "enum": [
+    "en",
+    "es",
+    "de",
+    "fr",
+    "it",
+    "nl",
+    "pt",
+    "bg",
+    "el",
+    "da",
+    "sv",
+    "no",
+    "fi",
+    "pl",
+    "ru"
+  ],
+  "type": "string"
+}

changedOutput schema / properties / agencies / items / properties / url / description

Previous value: -"The agency's public page."New value: +"The agency's page on PropertyList, in the language asked for; null when PropertyList shows no page for it."

changedOutput schema / properties / agencies / items / properties / url / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "agencies": {
+      "items": {
+        "properties": {
+          "city": {
+            "type": "string"
+          },
+          "id": {
+            "type": "integer"
+          },
+          "listing_count": {
+            "description": "Active listings it carries in the area.",
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "province": {
+            "type": "string"
+          },
+          "url": {
+            "description": "The agency's public page.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "listing_count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "agencies"
+  ],
+  "type": "object"
+}

First observedJul 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real value: a ranking rule, a nullable `url` edge case for agencies with no page, and a language-dependent link. The only blemish is 'Returns up to 10 agencies', which sits awkwardly against a `limit` parameter that allows up to 25.

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 ranking rule, and every sentence carries information. Slightly long for a three-parameter read tool, and the described 10-result cap duplicates and muddies the `limit` parameter.

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 values need not be enumerated, yet the description still summarizes the main fields and the null case. For a read-only, single-required-parameter lookup this is essentially complete; only the `limit` semantics remain unaddressed.

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% – `location` and `language` are documented, `limit` is not. The description clarifies that `language` controls the language of the linked agency page and that `url` may be null, but it never explains `limit` or reconciles it with the stated cap of 10, so it neither compensates for the gap nor misleads badly.

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 (find agencies in an area), the ranking basis (active listing count), and the payload returned (name, location, listing count, url). An agent can distinguish this from area_market_summary 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?

Gives an explicit situational trigger: use it after a buyer has narrowed in on an area and wants to know which agencies dominate it. It does not name a competing sibling (e.g. area_market_summary) or state when not to use it, so it stops 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?