Heimster – Swiss homes

Search homes on Heimster

search_listings

Read-onlyIdempotent

Searches homes and properties in Switzerland – to rent or buy, also by feel (ruhig, sonnig, lebendig/belebt, grün, zentral, familienfreundlich; calme, ensoleillé, animé; tranquillo, vivace) (Wohnung mieten/kaufen, Haus kaufen, WG-Zimmer, Studio; appartement à louer/acheter, maison; appartamento in affitto/in vendita; flat, apartment, house). Covers current listings on Heimster and on Swiss agency websites, with walking distance to supermarket, childcare (Kita, crèche), school, park, stop and train station; quiet locations (road/rail noise); sun score; and the door-to-door public-transport commute to the person's workplace (workplace + max_commute_min). Ask where they work when the commute matters. Filter by place, type, rooms, price and area; sort by newest or price.

Input Schema

Name	Required	Description
`sort`	No
`green`	No	Only green, family-friendly surroundings: parks & playgrounds within 500 m (grün, im Grünen, Natur, Spielplatz; verdure; verde).
`limit`	No
`place`	No	Municipality, postal code or canton in Switzerland, e.g. «Winterthur», «8004», «ZH».
`quiet`	No	Only quiet locations: road/rail noise by day below 55 dB at the facade.
`lively`	No	Only lively locations: many restaurants & cafés within 500 m on foot (belebt, lebendig, urban, Ausgang; animé; vivace). Use for «vivid area», «lots of restaurants», «where things happen».
`area_min`	No	Minimum living area in m².
`category`	No	rent (default), buy, shared_flat (WG room) or sublet.
`language`	No	Language of titles, descriptions and links (default de). Use the user's language.
`new_build`	No	Only units in new-build projects.
`price_max`	No	CHF; per month for rent, total for buy.
`price_min`	No	CHF; per month for rent, total for buy.
`rooms_max`	No
`rooms_min`	No	Swiss room count, e.g. 3.5
`workplace`	No	Where the user works or studies (address or place) – for the commute filter.
`max_park_m`	No	Max distance (m) to a park.
`max_stop_m`	No	Max distance (m) to a bus/tram stop.
`max_school_m`	No	Max distance (m) to a school.
`min_sun_score`	No	Minimum Heimster sun score (0–100, direct sun on the building/flat).
`property_type`	No
`max_childcare_m`	No	Max distance (m) to childcare (Kita) or kindergarten.
`max_commute_min`	No	Max door-to-door minutes by public transport to the workplace (default 30).
`max_supermarket_m`	No	Max walking distance (m) to a supermarket.
`max_train_station_m`	No	Max distance (m) to a train station.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 10, 2026

addedInput schema / properties / green

Added value: +{
+  "description": "Only green, family-friendly surroundings: parks & playgrounds within 500 m (grün, im Grünen, Natur, Spielplatz; verdure; verde).",
+  "type": "boolean"
+}

addedInput schema / properties / lively

Added value: +{
+  "description": "Only lively locations: many restaurants & cafés within 500 m on foot (belebt, lebendig, urban, Ausgang; animé; vivace). Use for «vivid area», «lots of restaurants», «where things happen».",
+  "type": "boolean"
+}

First observedOct 10, 2026

TDQS

B3.3/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 the safety profile is covered. The description does add one real behavioral fact beyond the annotations – that results span both Heimster and external Swiss agency websites – but says nothing about result volume, pagination, limits, or result freshness.

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

Conciseness2/5

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

The purpose is front-loaded, but the description is a dense wall of text with extensive parenthetical keyword dumps in German, French and Italian that duplicate the schema's own synonym lists. Much of the middle ('ruhig, sonnig, lebendig/belebt, grün, zentral, familienfreundlich; calme, ensoleillé, animé...') does not earn its space because the parameters already carry those synonyms.

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 24-parameter, zero-required search tool with no output schema, the description adequately conveys the filter surface (place, type, rooms, price, area, commute, proximity, feel) and the data sources, and annotations cover the safety profile. Gaps remain around zero-param behaviour, default sort, and the limit cap, but nothing critical for correct invocation is missing.

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 83%, so the schema already documents nearly every parameter, including the multilingual synonym mappings (green, quiet, lively). The description's only added value is a summary of filter categories ('place, type, rooms, price and area; sort by newest or price'), which largely restates the schema. Baseline 3 is appropriate.

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 states a specific verb and resource ('Searches homes and properties in Switzerland – to rent or buy') and covers the feel-based and proximity filters, so the agent knows exactly what this tool retrieves. However, it never names or contrasts sibling tools such as search_new_builds or the generic search, so differentiation from neighbours is left to inference.

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?

There is one genuinely actionable usage instruction ('Ask where they work when the commute matters'), which implies the commute filter requires an extra step. Beyond that there is no explicit when-to-use / when-not-to-use guidance and no routing to alternatives like search_new_builds for new-build projects or create_search_alert for saved searches.

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

All Heimster – Swiss homes 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?