Skip to main content
Glama

search_real_estate_data

Read-onlyIdempotent

Search opendata.swiss for Swiss real-estate and housing datasets covering prices, rents, construction, and vacancies. Enter DE, FR, or EN terms to find relevant open data.

Instructions

Search opendata.swiss for real-estate/housing datasets (prices, rents, construction, vacancies)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_real_estate_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo1–20
queryYesDE/FR/EN terms, e.g. Miete, logement, Leerwohnungen

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • addedInput schema / properties / limit / default
      Added value: +10
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (1–20, default 10)."New value: +"1–20"
    • changedInput schema / properties / query / description
      Previous value: -"Search terms in German, French, or English (e.g. \"Immobilien\", \"Miete\", \"rent\", \"logement\", \"Wohnungspreise\", \"Leerwohnungen\")."New value: +"DE/FR/EN terms, e.g. Miete, logement, Leerwohnungen"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds that results come from the opendata.swiss catalog and what subject matter is indexed, but says nothing about result shape, relevance ranking, or how the limit interacts with result quality.

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?

A single front-loaded sentence with no filler, and the source plus domain appear first. It is arguably under-sized for a tool whose main ambiguity is its relationship to other search tools, but nothing in it is wasted.

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 two-parameter read-only search with full schema coverage, no output schema, and complete annotation coverage, the description supplies source and topic scope, which is most of what an agent needs. The remaining gap is routing guidance against the generic opendata and property-index siblings.

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 both parameters are already documented, including multilingual query terms and the 1–20 limit range. The description's parenthetical list (prices, rents, construction, vacancies) hints at useful query vocabulary but is not tied explicitly to the query parameter, so it adds little beyond the schema.

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?

Uses a specific verb ("Search") with an explicit source (opendata.swiss) and topical scope (real-estate/housing: prices, rents, construction, vacancies). The domain scoping separates it from generic data siblings, but it does not distinguish itself from search_opendata, which presumably searches the same catalog.

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

Usage Guidelines2/5

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

There is no statement of when to use this instead of search_opendata, search_statistics, get_property_price_index, or get_rent_index, all of which sit in the same sibling list. An agent must infer the boundary from the topic words alone, and could easily pick the generic opendata search instead.

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

Deploy Server

Other Tools