Claro AI by Casafari

What premises ask in a place

claro_market_snapshot

Read-only

What commercial premises of a kind ask in a place in Spain, from every active property of that kind and place: the asking price per m² as a distribution with its median and middle half, by size band and by district or town, the monthly average over three years with the change in a year, the listings on the market and their days on the market. Ask in plain words or send criteria as data. Asking prices, not agreed ones; at least 10 listings or no figures. Costs 25 tokens a call.

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the text the answer writes (titles, notes, labels, reasons, error messages): en (default) or de (German). Place names, agency names, property titles and quotes from a property's own text stay as written.	en
`criteria`	No	Criteria as data. Hard criteria (operation, cities, types, price, area) exclude properties outside them; the rest exclude only properties that state the opposite, and each result says which were met and which the property does not state.
`question`	No	The question in plain words, any language: "what do offices rent for in Valencia?"

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / criteria / properties / districts / description

Previous value: -"Named districts or neighbourhoods in the cities (Centro, Malasaña, Chamberí, Eixample, Gràcia, Poblenou...). A property outside them is out; one that does not state its district stays, marked not stated."New value: +"Named districts or neighbourhoods in the cities (Centro, Malasaña, Chamberí, Eixample, Gràcia, Poblenou...). A property outside them is out; one that does not state its district stays, marked not stated, unless its map location is outside them."

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / criteria / properties / bbox

Added value: +{
+  "description": "A map viewport: only premises with a point inside {south, west, north, east} (degrees). Use it instead of cities, provinces and districts.",
+  "properties": {
+    "east": {
+      "type": "number"
+    },
+    "north": {
+      "type": "number"
+    },
+    "south": {
+      "type": "number"
+    },
+    "west": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 2, 2026

changedInput schema / properties / criteria / properties / footfall_min / description

Previous value: -"Minimum footfall index within a 5-minute walk (an index of pedestrian activity that compares places; not a head count). Needs location data access."New value: +"Minimum daily footfall within a 5-minute walk (estimated passers-by a day, added up over every 25 m of street; not a count of different people). Needs location data access."

Changed5 schema fields changedNov 1, 2026

changedInput schema / properties / criteria / properties / cities / description

Previous value: -"Towns or cities in the search's country by name or slug (\"valencia\", \"Palma\"; with country de: \"München\", \"koln\"). Leave out for the whole country."New value: +"Towns or cities in the search's country by name or slug (\"valencia\", \"Palma\"; with country de: \"München\", \"koln\"; with country pt: \"Lisboa\", \"Cascais\"). Leave out for the whole country."

changedInput schema / properties / criteria / properties / country / description

Previous value: -"The one country the search is in: es (Spain, the default) or de (Germany). Cities and provinces are that country's; counts never mix countries."New value: +"The one country the search is in: es (Spain, the default), de (Germany) or pt (Portugal). Cities and provinces are that country's; counts never mix countries."

changedInput schema / properties / criteria / properties / country / enum

Previous value: -[
-  "es",
-  "de"
-]New value: +[
+  "es",
+  "de",
+  "pt"
+]

changedInput schema / properties / criteria / properties / provinces / description

Previous value: -"Provinces in Spain, or Länder with country de (\"bayern\", \"nordrhein-westfalen\"); a property must be in one of them."New value: +"Provinces in Spain, Länder with country de (\"bayern\", \"nordrhein-westfalen\"), or distritos with country pt (\"lisboa\", \"porto\", \"arquipelago-da-madeira\"); a property must be in one of them."

changedInput schema / properties / criteria / properties / provinces / items / enum

Previous value: -[
-  "a-coruna",
-  "alava",
-  "albacete",
-  "alicante",
-  "almeria",
-  "asturias",
-  "avila",
-  "badajoz",
-  "barcelona",
-  "burgos",
-  "caceres",
-  "cadiz",
-  "cantabria",
-  "castellon",
-  "ceuta",
-  "ciudad-real",
-  "cordoba",
-  "cuenca",
-  "girona",
-  "granada",
-  "guadalajara",
-  "guipuzcoa",
-  "huelva",
-  "huesca",
-  "islas-baleares",
-  "jaen",
-  "la-rioja",
-  "las-palmas",
-  "leon",
-  "lleida",
-  "lugo",
-  "madrid",
-  "malaga",
-  "melilla",
-  "murcia",
-  "navarra",
-  "ourense",
-  "palencia",
-  "pontevedra",
-  "salamanca",
-  "santa-cruz-de-tenerife",
-  "segovia",
-  "sevilla",
-  "soria",
-  "tarragona",
-  "teruel",
-  "toledo",
-  "valencia",
-  "valladolid",
-  "vizcaya",
-  "zamora",
-  "zaragoza",
-  "baden-wurttemberg",
-  "bayern",
-  "berlin",
-  "brandenburg",
-  "bremen",
-  "hamburg",
-  "hessen",
-  "mecklenburg-vorpommern",
-  "niedersachsen",
-  "nordrhein-westfalen",
-  "rheinland-pfalz",
-  "saarland",
-  "sachsen",
-  "sachsen-anhalt",
-  "schleswig-holstein",
-  "thuringen"
-]New value: +[
+  "a-coruna",
+  "alava",
+  "albacete",
+  "alicante",
+  "almeria",
+  "asturias",
+  "avila",
+  "badajoz",
+  "barcelona",
+  "burgos",
+  "caceres",
+  "cadiz",
+  "cantabria",
+  "castellon",
+  "ceuta",
+  "ciudad-real",
+  "cordoba",
+  "cuenca",
+  "girona",
+  "granada",
+  "guadalajara",
+  "guipuzcoa",
+  "huelva",
+  "huesca",
+  "islas-baleares",
+  "jaen",
+  "la-rioja",
+  "las-palmas",
+  "leon",
+  "lleida",
+  "lugo",
+  "madrid",
+  "malaga",
+  "melilla",
+  "murcia",
+  "navarra",
+  "ourense",
+  "palencia",
+  "pontevedra",
+  "salamanca",
+  "santa-cruz-de-tenerife",
+  "segovia",
+  "sevilla",
+  "soria",
+  "tarragona",
+  "teruel",
+  "toledo",
+  "valencia",
+  "valladolid",
+  "vizcaya",
+  "zamora",
+  "zaragoza",
+  "baden-wurttemberg",
+  "bayern",
+  "berlin",
+  "brandenburg",
+  "bremen",
+  "hamburg",
+  "hessen",
+  "mecklenburg-vorpommern",
+  "niedersachsen",
+  "nordrhein-westfalen",
+  "rheinland-pfalz",
+  "saarland",
+  "sachsen",
+  "sachsen-anhalt",
+  "schleswig-holstein",
+  "thuringen",
+  "acores",
+  "arquipelago-da-madeira",
+  "aveiro",
+  "beja",
+  "braga",
+  "braganca",
+  "castelo-branco",
+  "coimbra",
+  "evora",
+  "faro",
+  "guarda",
+  "leiria",
+  "lisboa",
+  "portalegre",
+  "porto",
+  "santarem",
+  "setubal",
+  "viana-do-castelo",
+  "vila-real",
+  "viseu"
+]

Changed1 schema field changedOct 19, 2026

addedInput schema / properties / lang

Added value: +{
+  "default": "en",
+  "description": "Language of the text the answer writes (titles, notes, labels, reasons, error messages): en (default) or de (German). Place names, agency names, property titles and quotes from a property's own text stay as written.",
+  "enum": [
+    "en",
+    "de"
+  ],
+  "type": "string"
+}

First observedOct 17, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond them: the figures are asking prices rather than agreed/transaction prices, cohorts below 10 listings produce no figures at all, and each call costs 25 tokens — the last being operationally important for an agent. It does not describe ordering, pagination, or result limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is a long run-on packing five separate output dimensions into one clause chain, which makes it harder to scan than it needs to be. The three following sentences (input modes, price caveat, minimum cohort, cost) are tight and each earns its place, so the waste is in structure rather than content.

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?

There is no output schema, so the description must carry return-value semantics, and it does: distribution with median and middle half, segmentation by size band and district/town, a three-year monthly series with annual change, and listing counts with days on market. Against a 50+ field criteria object it is still thin on how criteria combine and on ordering of results, but the core shape is conveyed.

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% across a very large nested criteria object, so the schema does the heavy lifting and baseline 3 applies. The description does add one genuinely useful semantic point — that the same request can be expressed as free-text question or as structured criteria data — which explains the relationship between the two top-level inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and computation: asking price per m² as a distribution with median and middle half, by size band and by district or town, plus a three-year monthly average with year-on-year change and days on market. That is far more precise than the title 'What premises ask in a place'. It does not explicitly point at the sibling it is not (claro_search_premises for individual listings, claro_compare_premises for comparisons), so the differentiation is inferable rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the framing — this is the tool for 'what do premises of this kind ask here' market questions — and the minimum-10-listings rule tells the agent when results will be suppressed. However there is no explicit when-to-use versus claro_search_premises or claro_compare_premises, and no statement of what this tool is not for.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Claro AI by Casafari 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?