Skip to main content
Glama

PropertyList: Spanish Property MLS

by es.propertylist
OverviewDiscussionsAdmin

Autocomplete location

autocomplete_location
Read-onlyIdempotent

Look up property areas (city, suburb, urbanisation, or a group of areas such as a region or a coast) by free-text name. Returns up to 10 matches with id, name, type, the parent province/city and the number of listings, biggest first, so a group that covers a whole region (e.g. 'Region of Murcia') comes before the city of the same name. Use this to resolve place names before calling search_properties, especially for common spellings like 'Nueva Andalucia' (vs 'Nueva Andalucía') or 'Marbella old town', and pass the chosen id to search_properties as location_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesFree-text place name. 2+ characters.
provincesNoOptional comma-separated province ids to scope the search.
search_typeNoMarket the listing counts and the ranking are for. Defaults to 'for-sale'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / search_type
      Added value: +{
+  "description": "Market the listing counts and the ranking are for. Defaults to 'for-sale'.",
+  "enum": [
+    "for-sale",
+    "for-rent",
+    "holiday-rentals"
+  ],
+  "type": "string"
+}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "matches": {
+      "items": {
+        "properties": {
+          "areas_in_group": {
+            "description": "For a group: how many areas it is made of.",
+            "type": "integer"
+          },
+          "id": {
+            "description": "Area id: pass it to search_properties as location_id.",
+            "type": "integer"
+          },
+          "kind": {
+            "description": "The raw area level, kept for existing callers; read type instead.",
+            "type": [
+              "string",
+              "integer"
+            ]
+          },
+          "listings": {
+            "description": "Live listings in it for the search_type asked for.",
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "parent": {
+            "description": "The area this one sits in.",
+            "type": "string"
+          },
+          "province": {
+            "type": "string"
+          },
+          "type": {
+            "description": "What kind of place it is; a group is a region or a coast made of other areas.",
+            "enum": [
+              "city",
+              "suburb",
+              "urbanisation",
+              "group",
+              "area"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "type",
+          "listings"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "matches"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description still adds real behavioral detail beyond that: result cap (10), ordering rule (biggest first), and the tie-break that a region group precedes a same-named city. It does not mention truncation or empty-result behavior, so it falls just short of 5.

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?

Two sentences that are front-loaded with the resource and followed by the routing guidance; every clause carries information. Slightly dense parenthetical enumerations of area types, but 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?

With an output schema present the description need not detail return values, yet it still summarizes them (id, name, type, parent, listing count, ranking). Inputs, ranking semantics, and the downstream call are all covered, so an agent has everything needed to invoke it 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?

Schema description coverage is 100%, so all three parameters (query, provinces, search_type) are already documented in the schema. The description adds only indirect meaning, e.g. that ranking and counts depend on the market implied by search_type, which is largely restated from the schema. Baseline 3 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?

The description states a specific verb (look up) and resource (property areas: city, suburb, urbanisation, region/coast group), naming the accepted input (free-text name). It is clearly distinguishable from siblings like search_properties, which it explicitly feeds into.

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?

It states when to use it ('resolve place names before calling search_properties'), covers the tricky case with concrete examples ('Nueva Andalucia' vs 'Nueva Andalucía', 'Marbella old town'), and specifies the handoff ('pass the chosen id to search_properties as location_id'). No inference required.

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 toolsInspect
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