Skip to main content
Glama

Ferienhausmiete.de – Ferienwohnungen & Ferienhäuser suchen

Search accommodations

search_accommodations
Read-onlyIdempotent

Paginated holiday accommodation search over directly bookable/inquirable own inventory (externally managed listings are not exposed). Filter by region (regionId from autocomplete_regions), a radius around a point (lat/lng/radiusKm — use the coordinates of the place the user names; results then carry distanceKm and can be sorted by distance) or a map bounding box (neLat/neLng/swLat/swLng); these three are mutually exclusive. Travel dates (arrival/departure, both together; add bookableOnly to drop stays below the minimum stay), persons (a minimum: beds ≥ persons — add personsMax to exclude oversized houses; optional adults split for families — children can use extra-children slots), bedrooms, bathrooms, livingSpaceMin (m²), minReviews, price range per night, feature codes (e.g. swimming_pool, wifi, pets_allowed), accommodation types and offers. Sort: relevance (default), rating (best first; website formula, a single 5.0 review outranks many 4.8s — use minReviews), persons, bedrooms, living_area, distance (radius searches). Every result carries url (the listing page on the website of the locale) and, on dated searches, stayUrl with dates and guests pre-filled — give these to the user as the link. location.place is the actual town; location.region is the (marketing) region it is listed under. Dated searches include a stayPrice per result: the exact total for the stay incl. mandatory costs and discounts (kind "total"; "min_stay" when the stay is below the minimum), or "from"/"on_request" where only the static basePrice or no price is available. approximate: true means some nights were priced from the owner's base price; the website confirms the final total.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoSearch centre latitude
lngNoSearch centre longitude
pageNo
sortNorelevance
neLatNoBounding box north-east latitude
neLngNoBounding box north-east longitude
queryNoKeyword search over names and descriptions in the response language and the German originals
swLatNoBounding box south-west latitude
swLngNoBounding box south-west longitude
typesNo
adultsNoAdults among persons; when below persons, objects may host the remainder as extra children (website guests widget parity)
localeNoLanguage the user is writing in (de, en, fr, pl, it, es, nl, hr); defaults to de. Selects the language of names and texts in the response and the language region names are matched in — pass it on every call.de
offersNo
arrivalNo
perPageNo
personsNoMinimum sleeping places (beds ≥ persons); combine with personsMax to cap size
bedroomsNo
featuresNo
priceMaxNoOmit for unbounded — no sentinel values
priceMinNoPer night with dates, base price without
radiusKmNoRadius around the centre in km (as the crow flies), max 300
regionIdNoRegion to search in (from /regions/autocomplete); omit to search everywhere
bathroomsNo
departureNo
minReviewsNoOnly accommodations with at least this many visible reviews
personsMaxNoMaximum sleeping places (beds ≤ personsMax); excludes oversized houses
bookableOnlyNoDated searches only: keep only stays that meet the minimum stay (drops stayPrice.kind "min_stay" results)
livingSpaceMinNoMinimum living space in m²

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare the safe read-only/idempotent profile, and the description layers on substantial behavioral detail beyond them: pagination, the url/stayUrl fields to hand to the user, the meaning of location.place vs location.region, and the full stayPrice semantics including kind 'total'/'min_stay'/'from'/'on_request' and the approximate flag.

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?

The purpose is front-loaded and nearly every clause carries information, but the entire body is one dense semicolon-chained paragraph that is hard to parse for a 28-parameter tool. It earns its length; it would benefit from clearer segmentation.

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?

Despite having no output schema, the description explains the returned shape (url, stayUrl, location fields, stayPrice, approximate), covers the filter interactions, and gives sort behavior. An agent can call this correctly without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 28 params and only 64% schema description coverage, the description carries extra weight and delivers: mutual exclusivity of the geo filters, persons as a minimum with beds ≥ persons, personsMax to exclude oversized houses, adults/extra-children split, bookableOnly dropping min_stay stays, distance sorting only on radius searches, and per-night vs base price semantics.

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?

States a specific verb+resource (paginated holiday accommodation search) and sharply bounds scope: only directly bookable/inquirable own inventory, with externally managed listings excluded. It does not name or distinguish against the sibling tools (get_accommodation, get_accommodation_availability), so it falls just short of a 5.

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

Usage Guidelines4/5

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

Provides strong operational context: it names the mutually exclusive geometry options (regionId vs lat/lng/radiusKm vs bounding box), tells the agent to use the coordinates of the place the user names, and points to autocomplete_regions as the source for regionId. However, it never says when to prefer this tool over the get_accommodation siblings, so no explicit alternative routing.

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