Skip to main content
Glama

Claro AI by Casafari

Get one premises

claro_get_premises
Read-only

One premises in full by the id a search returned: its data, the facts read from its text with the sentence each came from, its coordinates, up to 8 photos, its asking-price timeline, whether it is still on the market and the agency's own ad links. insights adds charts as data: asking prices against comparable premises nearby, nearby businesses, supply and time on the market, and Location Intelligence ranks when the plan includes it. assessment, with insights, adds an AI-written site assessment whose every number is checked against those figures. On the Free plan, only for ids your searches returned. Costs 25 tokens a call.

Input Schema

NameRequiredDescriptionDefault
idYesA premises id (pm_...) from a search result.
langNoLanguage 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
insightsNo
segmentsNoOptional, with insights: the business kinds whose distances come first in the distances chart, usually the brief's competitors (for a coffee shop: coffee and bakery). Without it the chart keeps its default order.
assessmentNoWith insights: add `site_assessment` first, a site assessment written by Gemini from this premises' own figures only (its data, its facts with their quotes, the market and competition charts, its parcel's zoning when `parcel_zoning` has an answer, its parcel's Cadastre record when `cadastre` has one (the register beside the advertised figures, with no verdict), and with location access the location figures and ranks): 3 to 5 summary sentences, strengths and watch-outs, and a verdict (strong, fair, weak, not_assessable) for quick-service restaurants, coffee and bakery, clinic and pharmacy, fitness, fashion and retail, and supermarket and convenience, each reason with the keys of the figures it rests on. Every number is checked against those figures and a sentence that fails is dropped (counted in `notes`); a missing figure is not stated, never a weakness. `scope` is with_location or listing_only. Stored per premises and inputs; the first request for new inputs waits for the model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assessment / description
      Previous value: -"With insights: add `site_assessment` first, a site assessment written by Gemini from this premises' own figures only (its data, its facts with their quotes, the market and competition charts, its parcel's zoning when `parcel_zoning` has an answer, and with location access the location figures and ranks): 3 to 5 summary sentences, strengths and watch-outs, and a verdict (strong, fair, weak, not_assessable) for quick-service restaurants, coffee and bakery, clinic and pharmacy, fitness, fashion and retail, and supermarket and convenience, each reason with the keys of the figures it rests on. Every number is checked against those figures and a sentence that fails is dropped (counted in `notes`); a missing figure is not stated, never a weakness. `scope` is with_location or listing_only. Stored per premises and inputs; the first request for new inputs waits for the model."New value: +"With insights: add `site_assessment` first, a site assessment written by Gemini from this premises' own figures only (its data, its facts with their quotes, the market and competition charts, its parcel's zoning when `parcel_zoning` has an answer, its parcel's Cadastre record when `cadastre` has one (the register beside the advertised figures, with no verdict), and with location access the location figures and ranks): 3 to 5 summary sentences, strengths and watch-outs, and a verdict (strong, fair, weak, not_assessable) for quick-service restaurants, coffee and bakery, clinic and pharmacy, fitness, fashion and retail, and supermarket and convenience, each reason with the keys of the figures it rests on. Every number is checked against those figures and a sentence that fails is dropped (counted in `notes`); a missing figure is not stated, never a weakness. `scope` is with_location or listing_only. Stored per premises and inputs; the first request for new inputs waits for the model."
  2. Changed1 schema field changed
    • changedInput schema / properties / assessment / description
      Previous value: -"With insights: add `site_assessment` first, a site assessment written by Gemini from this premises' own figures only (its data, its facts with their quotes, the market and competition charts, and with location access the location figures and ranks): 3 to 5 summary sentences, strengths and watch-outs, and a verdict (strong, fair, weak, not_assessable) for quick-service restaurants, coffee and bakery, clinic and pharmacy, fitness, fashion and retail, and supermarket and convenience, each reason with the keys of the figures it rests on. Every number is checked against those figures and a sentence that fails is dropped (counted in `notes`); a missing figure is not stated, never a weakness. `scope` is with_location or listing_only. Stored per premises and inputs; the first request for new inputs waits for the model."New value: +"With insights: add `site_assessment` first, a site assessment written by Gemini from this premises' own figures only (its data, its facts with their quotes, the market and competition charts, its parcel's zoning when `parcel_zoning` has an answer, and with location access the location figures and ranks): 3 to 5 summary sentences, strengths and watch-outs, and a verdict (strong, fair, weak, not_assessable) for quick-service restaurants, coffee and bakery, clinic and pharmacy, fitness, fashion and retail, and supermarket and convenience, each reason with the keys of the figures it rests on. Every number is checked against those figures and a sentence that fails is dropped (counted in `notes`); a missing figure is not stated, never a weakness. `scope` is with_location or listing_only. Stored per premises and inputs; the first request for new inputs waits for the model."
  3. Changed1 schema field changed
    • 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"
      +}
  4. Changed1 schema field changed
    • removedInput schema / properties / insights / description
      Removed value: -"Add `insights`, charts as data, each with a one-sentence answer, its count, scope, source and date: its asking price per m² against comparable premises nearby (same type, operation and district, half to twice its size), footfall by part of the day and where its location figures rank in the city (location access only), straight-line distances to businesses of each kind within 1 km (Overture Maps), other premises on the market within 500 m, and the monthly average asking price per m² of its type in its town over three years with the change in a year (Casafari Area Insights); `prices_here`, what active properties of its type ask per m² for rent and for sale in its district (then town, then province: the first with 10 priced units), quartiles from 10 and medians from 5, the town's rows beside it and medians by size band; `supply_flow`, from Claro's nightly count (`market_daily`, since 8 Oct 2026): units of its type and operation on the market in its town (or province) on the latest day, properties that came on and left over 30 days, and the median asking price per m² at both ends, with a note when fewer than 7 days are recorded; and `time_on_market`, the average days on the market by asking price band of properties of its type within 1 km (Casafari Area Insights; the ~500 m cell's centre when the address is hidden); and `similar`: up to six other active premises of the same type and operation, half to twice its size, within 1.5 km (from the ~500 m cell's centre for a hidden address), else its district, else its town, nearest first then closest in asking price per m², each with its id, one Casafari thumbnail and the agency's own listing page only (never a portal or a private seller). Asking prices, not agreed ones; each unit counted once. Also adds `nearby`, the map's layers: businesses of the tracked kinds within 500 m (Overture Maps; exact addresses only) and other premises on the market within 500 m as points, nearest first (a hidden address as the centre of its ~500 m cell), and the area a 5-minute walk reaches as GeoJSON MultiPolygon coordinates (location access and an exact address only). With location access and an exact address, `location_detail`: figures in groups (reach, residents, visitors, health_education, transport_parking, offices_hotels, retail_food), each with a stable key, label, value, unit, scope, source, date and a percentile in the city for figures stored for every property; the 10 nearest named places per kind with walking minutes (OpenStreetMap through Location Intelligence); and the 10-minute walk. A figure Location Intelligence does not have for the point is left out, never 0. With location access, `scorecard`: every location figure held for the premises (the stored location row, `location_detail`, `footfall_detail` and `access`), grouped as `location_detail` is, each with its scope, source and date and, for figures stored for every property, its percentile among premises of its type in the city (`city`) and in its district when 50 or more are measured there (`district`): the share with a lower figure, each unit once. Live figures carry no percentile and a note saying so; a 0 footfall or population is unknown and never ranked. `strongest` and `weakest` name the five row keys with the highest and lowest city percentiles."
  5. 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 and non-destructive behavior, so the description adds value by disclosing a hard cost (25 tokens per call) and a Free-plan eligibility constraint. It also explains that insights gates charts and that assessment requires insights and may wait on a model call, though the caching detail itself lives mostly in the schema text.

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?

It is a single dense block but front-loaded: the core action and return contents come first, then the optional enhancements, then plan and cost constraints. A few clauses are long, yet every sentence carries operational information rather than 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 no output schema, the description carries the burden of describing the return payload and does so thoroughly, enumerating data, facts, photos, timeline, market status, ad links, charts and the optional assessment. An agent can decide whether to spend the tokens knowing what it will receive.

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 80%, so most parameters are already documented. The description still adds meaning beyond the schema by spelling out what the insights charts contain and the dependency that assessment only produces a site assessment when insights is set, which is more than the bare schema default conveys.

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 opens with a specific verb and resource ("One premises in full by the id a search returned") and then enumerates exactly what comes back: data, extracted facts with source sentences, coordinates, up to 8 photos, asking-price timeline, market status and agency ad links. This clearly distinguishes it from siblings like claro_search_premises and claro_compare_premises.

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?

It states the prerequisite that the id must come from a search result, and gives a plan-level restriction ("On the Free plan, only for ids your searches returned") plus the token cost. It does not explicitly route the agent away from claro_compare_premises for multi-premises comparison, which keeps it 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources