Skip to main content
Glama

immobilien

search_properties

Sucht Immobilienanzeigen zur Miete und zum Kauf in Österreich, Deutschland und der Schweiz (immokralle.com) und liefert eine kompakte Liste (id, title, offer_type, property_type, price, currency, area_m2, rooms, location, date). Mindestens query, location oder country angeben; alle Filter sind kombinierbar. Der Link zum Exposé ist NICHT in der Liste enthalten — für Details und den klickbaren Link rufe fetch_property mit der id auf. price ist bei Miete die Monatsmiete laut Quelle, bei Kauf der Kaufpreis; Währung EUR, in der Schweiz meist CHF. null bei price, area_m2 oder rooms heißt: keine Angabe in der Anzeige. Sobald ein Preis-, Flächen- oder Zimmerfilter gesetzt ist, fallen Anzeigen ohne diese Angabe heraus. Sortierung: neue Anzeigen zuerst, darin relevantere zuerst. Bei 0 Treffern ist results leer und next_cursor null. Blättern nur über das zurückgegebene next_cursor möglich; die Seitenzahl ist begrenzt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoFreitext in Titel und Beschreibung, z.B. "Altbau Balkon" oder "Penthouse". Optional.
cursorNonext_cursor aus einer vorherigen Antwort, um die nächste Seite zu laden.
countryNoStrikt auf ein Land einschränken: AT (Österreich), DE (Deutschland) oder CH (Schweiz). Kombinierbar mit location.
area_maxNoHöchstfläche in m².
area_minNoMindestfläche in m².
locationNoOrt, PLZ, Bezirk oder Bundesland, z.B. "Wien", "1070", "Graz" oder "Bayern".
price_maxNoHöchstpreis (Monatsmiete bzw. Kaufpreis) in EUR bzw. CHF.
price_minNoMindestpreis (Monatsmiete bzw. Kaufpreis) in EUR bzw. CHF.
rooms_maxNoHöchstanzahl Zimmer.
rooms_minNoMindestanzahl Zimmer.
offer_typeNomiete oder kauf.
max_age_daysNoNur Anzeigen, die höchstens so viele Tage alt sind (z.B. 30). Ohne Angabe: kein Altersfilter.
property_typeNoObjektart.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full behavioral burden and does so: null semantics for price/area_m2/rooms, the non-obvious side effect that setting a price/area/room filter silently drops listings lacking that field, sort order (newest first, then relevance), and the 0-result shape (empty results, next_cursor null). It also constrains pagination to the returned cursor with a bounded page count.

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?

Purpose and the required-parameter constraint are front-loaded, and nearly every sentence carries operational information. It is a dense single paragraph, though, and the closing remark that the page number is limited is vague enough to be near-redundant with the cursor-only paging statement.

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?

For a 13-parameter search tool with no output schema, the description covers the returned field set, null handling, filtering side effects, sort order, empty-result shape, and pagination mechanism. An agent has everything needed to call it correctly and interpret the response.

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 schema already documents all 13 parameters; the description nonetheless adds meaning beyond it by defining price as monthly rent vs. purchase price depending on offer_type, noting EUR with CHF in Switzerland, and explaining how null values interact with range filters. It does not add syntax hints for cursor beyond what the schema says, keeping it just short of a 5.

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 (search real estate listings for rent and purchase in AT/DE/CH via immokralle.com) and enumerates the returned fields, so an agent knows exactly what comes back. It also names the sibling fetch_property and explains the division of labor (list vs. detail/link), which distinguishes it 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 Guidelines5/5

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

Explicitly requires at least one of query, location, or country, states that all filters are combinable, and routes the agent to fetch_property when a clickable exposé link or full details are needed. The when-to-use and when-to-use-something-else conditions are both present.

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