Somantic – German Real Estate Search

Search listings

search_listings

Read-only

Search current real-estate listings in Germany, newest first.

Returns listings with facts, Somantic's valuation (somantic_valuation_eur, price_vs_valuation_pct: negative means priced below it) and source_url, the original listing on the portal that carries the offer.

last_seen is when Somantic last confirmed the offer as online. Listings no longer confirmed are usually removed from results after 3 days.

One offer is often advertised on several portals at once. Those copies are collapsed to the newest, so a page can hold fewer than per_page listings and total counts the copies rather than the offers.

Input Schema

Name	Required	Description	Default
`q`	No	Where — a city ("München", "Frankfurt am Main") or a postcode ("80331").
`page`	No	Result page, starting at 1.
`vacant`	No	Only listings that are vacant (bezugsfrei).
`roi_min`	No	Minimum gross rental yield in percent, e.g. 5 for 5 %. Purchases only.
`features`	No	Required amenities. "new_building" keeps only new builds (Neubau, Erstbezug, or built within the last 3 years).
`per_page`	No	Results per page, at most 50.
`property`	No	"wohnung" (apartment) or "haus" (house).	wohnung
`size_max`	No	Maximum living space in m².
`size_min`	No	Minimum living space in m².
`year_max`	No	Built before this year.
`year_min`	No	Built in or after this year.
`price_max`	No	Maximum price in EUR; monthly cold rent when transaction is "mieten".
`price_min`	No	Minimum price in EUR; monthly cold rent when transaction is "mieten".
`rooms_max`	No	Maximum number of rooms.
`rooms_min`	No	Minimum number of rooms (German count, e.g. 2.5).
`transaction`	No	"kaufen" to buy, "mieten" to rent.	kaufen
`energy_class`	No	Energy efficiency classes, e.g. "A+,A,B".
`price_change`	No	Only listings whose price changed while listed: "reduced", "increased" or "any".
`price_per_sqm_max`	No	Maximum price per m² in EUR; cold rent per m² when transaction is "mieten".
`price_per_sqm_min`	No	Minimum price per m² in EUR; cold rent per m² when transaction is "mieten".
`renovation_needed`	No	Only listings that need renovation (renovierungsbedürftig).
`price_below_market`	No	Only listings priced below Somantic's valuation.
`exclude_erbbaurecht`	No	Leave out leasehold (Erbbaurecht) properties.
`exclude_foreclosures`	No	Leave out foreclosure auctions (Zwangsversteigerungen).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4/5.0

Behavior5/5

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

Annotations already declare readOnly/closed-world/non-destructive, but the description adds substantial behavior: multi-portal copies are collapsed to the newest (so a page can hold fewer than per_page and total counts copies, not offers), last_seen means last confirmed-online, and stale offers drop out after ~3 days. These are non-obvious result-shaping rules not present in the structured fields.

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 is front-loaded and no sentence is filler; the dedup/pagination caveat is genuinely necessary. It is slightly long across four paragraphs, but each block carries distinct, useful information.

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 24-parameter, zero-required search tool with full schema coverage and an output schema, the description closes the remaining gaps: result ordering, dedup collapsing, total-count semantics, and listing freshness. Nothing an agent needs to call or interpret results correctly 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 coverage is 100% across 24 parameters, so the schema already documents every filter. The description adds indirect context (the valuation fields that back price_below_market / price_vs_valuation_pct, and the source_url return), but no filter syntax or semantics beyond the schema, so the baseline 3 applies.

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+resource+scope: 'Search current real-estate listings in Germany, newest first.' The search semantics are clearly distinct from the sibling get_listing (single record) and estimate_value (valuation), so an agent can select it without opening the schema.

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?

The description never says when to use this tool versus get_listing or estimate_value, nor any preconditions or exclusions. Usage is only inferable from the purpose statement; there is no routing guidance.

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

All Somantic – German Real Estate Search 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?