Skip to main content
Glama
Sign In

Claro AI by Casafari

by com.casafari
OverviewDiscussionsAdmin

Search commercial plots (Germany)

claro_search_plots
Read-only

Find plots of land for sale or rent in Germany for a commercial building, one result per plot however many agencies advertise it. Criteria are data: regions (Länder), municipalities, postcodes, plot type, operation, plot area, price and price per m², keywords, and commercial_use, how far the property's own text says a commercial building can go on the plot. limit up to 50, capped by the plan; offset for the next page. On the Free plan, each call (and each page) is one of 4 searches. Costs 100 tokens a call. Each page is a call.

Input Schema

NameRequiredDescriptionDefault
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
sortNocommercial_use: strongest commercial-use level first; newest: latest on the market; price_asc: lowest sale price; area_desc: largest plot; price_m2_asc: lowest sale price per m².commercial_use
limitNoResults per page.
offsetNoResults to skip, for the next page.
criteriaNoCriteria as data, every field optional (leave out or send {} for all plots): regions, municipalities, zipcodes, plot_types, operation, plot_area_min, plot_area_max, sale_price_min, sale_price_max, sale_price_m2_max, commercial_use, serviced, keywords, exclude_keywords.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / criteria / description
      Previous value: -"Criteria as data, every field optional (leave out or send {} for all plots): regions, municipalities, zipcodes, plot_types, operation, plot_area_min, plot_area_max, sale_price_min, sale_price_max, sale_price_m2_max, commercial_use, serviced, keywords."New value: +"Criteria as data, every field optional (leave out or send {} for all plots): regions, municipalities, zipcodes, plot_types, operation, plot_area_min, plot_area_max, sale_price_min, sale_price_max, sale_price_m2_max, commercial_use, serviced, keywords, exclude_keywords."
    • addedInput schema / properties / criteria / properties / exclude_keywords
      Added value: +{
+  "description": "Leave out plots whose text states any of these. A plot that only denies one stays: exclude \"Erbbaurecht\" keeps a plot saying \"kein Erbbaurecht\".",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • changedInput schema / properties / criteria / properties / keywords / description
      Previous value: -"Words or phrases the property's text must contain, all of them: \"Gleisanschluss\", \"Autobahn\"."New value: +"Words or phrases the property's text must state, all of them, as whole words: \"Gleisanschluss\", \"Erbbaurecht\". A mention the text denies (kein, keine, nicht, ohne, nie, weder before it; nicht, nie, nein, ausgeschlossen right after) does not count; the sentence that states each is in keyword_matches."
  2. 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"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare a safe read-only, closed-world operation, and the description adds real value beyond them: deduplication across agencies, token cost per call, plan-based limit capping, and the rule that each page counts as a separate call and search. Result format is not described, but no output schema exists to cover it either.

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

Conciseness5/5

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

Front-loads what the tool returns and the dedup guarantee, then criteria, then the cost/quota rules. The criteria list is dense but mirrors the nested schema compactly; no filler sentences.

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?

For a tool with a nested criteria object, zero required parameters, and no output schema, the description covers cost, quota, pagination, deduplication and the semantics of the trickiest filter. It omits what a result looks like, which is the main remaining gap.

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 100%, so the baseline is 3, but the description adds meaning the schema does not: commercial_use is glossed as how far the property's own text says a commercial building can go, and limit is described as capped by the plan rather than only by the schema maximum of 50.

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 plots of land for sale or rent in Germany for a commercial building") and adds a distinguishing behavioral fact: one result per plot regardless of how many agencies advertise it. This differentiates it cleanly from the premises-oriented siblings without needing to name them.

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?

Gives useful operational guidance about paging (limit/offset, each page is a call) and the Free plan's 4-search allowance, which shapes how an agent should call it. However, it never says when to prefer this over claro_search_premises, claro_refine_search, or claro_get_plot, so tool selection is left to inference.

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