Skip to main content
Glama

Search Slowhop slow stays (cabins, agritourism, glamping)

slowhop_search

Search slowhop.com, the Polish marketplace of 'slow' stays: houses and cabins in nature, agritourism, guesthouses, glamping, tiny houses and apartments with character, mostly in Poland (some in Czechia, Slovakia, Italy, Croatia…). Filter by place (region, town, country or a landscape word), check-in/check-out dates and party — adults, children's ages, pets (with dates only places free for that party are returned, priced for it) — plus Slowhop's own filters (by a lake, by the sea, in the mountains, sauna, hot tub, breakfast, pets welcome…), a nightly price range and last-/first-minute deals; sort by recommendation or price. Returns one page (24 by default) in Slowhop's order; pass a listing's slug to slowhop_place for the description, units, house rules, pets policy and the exact price breakdown. Fetched live from Slowhop's own JSON API (typically well under 1 s via direct fetch; more when it falls back to an unblocker). Result shape: { source, fetchedAt, query, search_url, resolved_place: { name, kind, radius_km? } | null, alternatives?, stay: { date_from, date_to, nights } | null, guests: { adults, children_ages, pets }, total_count, page, total_pages, count, listings: [...], note? } — the list key is listings; total_count counts matches across all pages (use page for more). Each listing: { available, restriction, id, slug, name, url, type, type_key, city, region, country, summary, price, price_per_night, price_per_night_before_discount, currency, cheapest_dates, meal_plan, max_guests, units_for_party, rating, reviews_count, instant_booking, only_on_slowhop, for_whom, host, image }. Prices are numbers in the listing's currency — PLN for places in Poland, usually EUR abroad — for the WHOLE party, never per person. WITH date_from + date_to: price_per_night is Slowhop's nightly price for this party averaged over the stay (it already includes cleaning, pet and children's fees) and price = price_per_night × nights, the total for the whole stay (within a few zł of the booking total; slowhop_place with the same dates gives the exact breakdown); units_for_party > 1 means it covers several houses/rooms; url opens the place with the same stay. Dated, the site also lists places it cannot book exactly as asked — each listing's available is true (bookable as asked) or false, with restriction { type: min_nights | max_nights | arrival_impossible | departure_impossible | stay_impossible, min_nights, max_nights } saying why; those have price null (price_per_night stays their nightly rate for those dates), come last, and the note counts them — never quote an available: false place for the dates asked; slowhop_place with the same dates gives the exact quote before booking. WITHOUT dates available is null, price is null, price_per_night is the lowest upcoming nightly price and cheapest_dates says for which stay; availability is not checked (the note says so). price_per_night_before_discount is set during a last-/first-minute discount. meal_plan is none | breakfast | half_board | full_board | all_inclusive; rating is 0–5 (null without reviews). An empty match answers count: 0 with a note saying why and what to change — that is a successful result, not an error.

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, 1-based. Default 1.
petsNoThe animals coming along, one entry each: 'small_dog', 'medium_dog', 'big_dog', 'cat' (e.g. ['big_dog', 'cat']). Also limits results to places that accept them. Default none.
sortNo'recommended' (Slowhop's order, default), 'price_asc' or 'price_desc' (by nightly price).
limitNoPlaces per page, 1–48. Default 24.
placeNoWhere, resolved by Slowhop's own autocomplete: a region ('Mazury', 'Bieszczady', 'Kaszuby', 'Tatry', 'Roztocze', 'Toskania'), a town ('Zakopane', 'Kazimierz Dolny' — searched within radius_km), a country ('Chorwacja', 'Włochy'), or a landscape word ('góry', 'morze', 'jezioro', 'las', 'wieś' → Poland with that setting filter). Polish names work best. Omit to search everywhere.
adultsNoAdults. Default 2.
date_toNoCheck-out date, YYYY-MM-DD, after date_from (at most 60 nights).
filtersNoSlowhop's own filter ids. Alternatives of one kind match ANY — settings, types, who-for, accepted pets, the wellness facilities sauna/wooden_bath/pool/jacuzzi/bathtube/massages — while different kinds must ALL match (['lake', 'sauna'] = by a lake AND with a sauna; ['sauna', 'jacuzzi'] = either): the site's own logic. Setting: lake, sea, mountain, forest, countryside, shoreline, river, city. Type: agro_guesthouse (agritourism, guesthouse), cottages (houses incl. tiny houses), tiny_house, camping (glamping/camping), hotels, city_apartments, hostels, campers, yachts. Who for: children_loving, couples, without_neighbors, adults (adults and teens only), rarities, unique_view, good_design, modern_architecture, idyllic, historical_places, fixer_upper, pet-free, lots_of_animals, single, disability, celebrations, workshops_and_conferences. Food: breakfast, meals (meals on site), restaurant, kitchen_available, vegetarian, vegan, special_diets. Pets: small_dogs, medium_dogs, big_dogs, cats, fenced_area, leash_free. Wellness: sauna, wooden_bath (outdoor hot tub, 'balia'), pool, jacuzzi, bathtube, massages, fireplace. Active: forest-trails, trail (mountain trail), skiing-slope, running-ski (cross-country skiing), horseriding, kayaks, fishing, bikes_onsite. Other: solo / groups (workation), fast_internet, no_internet, electric-car-charger, kids-playground.
no_cacheNoForce a fresh fetch and bypass this server's result cache (5 min). Default false.
date_fromNoCheck-in date, YYYY-MM-DD, today or later. Pass together with date_to; without dates prices are the lowest upcoming 'from' prices and availability is not checked.
price_maxNoMaximum nightly price for the whole party, in PLN (Slowhop converts foreign prices).
price_minNoMinimum nightly price for the whole party, in PLN (Slowhop converts foreign prices).
radius_kmNoAround a town only: search radius in km (default: the site's own, 20 km for a town).
last_minuteNoOnly last-minute deals. Default false.
first_minuteNoOnly first-minute (early booking) deals. Default false.
children_agesNoEach child's age in years (0–17), e.g. [4, 9] for two children — prices depend on ages. Default none.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageYes
stayNo
countYes
queryYes
guestsNo
sourceYes
listingsYes
fetchedAtYes
search_urlYes
total_countNo
total_pagesNo
alternativesNo
resolved_placeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does so thoroughly: caching (5 min, `no_cache` bypass), fetch latency including unblocker fallback, currency and per-whole-party pricing rules, the `available: false` / `restriction` semantics, and the crucial note that an empty match with `count: 0` and a `note` is a successful result rather than an error. This is exactly the operational context that prevents misreading results.

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

Conciseness3/5

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

Purpose and mode-switching are front-loaded, but the body becomes a dense block of near-run-on prose covering output fields, price arithmetic, restriction types and empty-result behavior in long semicolon-chained sentences. Much of it is valuable, yet the output-field explanation overlaps the existing output schema and the 'slowhop_place with the same dates gives the exact...' point is restated twice.

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 16-parameter search tool with no annotations, the description covers everything an agent needs: scope, date-dependent semantics, price units, availability flags, sorting, pagination via `page`/`total_count`, and the success-vs-error distinction for empty results. Nothing required to call it correctly is missing.

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 baseline is 3, but the description adds genuine meaning beyond the schema: `place` resolution behavior (autocomplete, town radius via `radius_km`), that `price_min`/`price_max` are nightly prices for the whole party in PLN with foreign prices converted, and how party composition affects returned pricing. It does not add much on `filters` beyond the schema's own enumeration, keeping it 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?

Opens with a specific verb and resource ('Search slowhop.com, the Polish marketplace of slow stays') and immediately enumerates the property types covered (cabins, agritourism, glamping, tiny houses). It explicitly routes downstream detail to the sibling: 'pass a listing's `slug` to slowhop_place for the description, units, house rules...', so the agent can separate search from detail without reading 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 states the two modes of use and their consequences: WITH dates availability is checked and unbookable places are flagged, WITHOUT dates availability is not checked and prices are 'from' prices — plus the directive 'never quote an available: false place for the dates asked'. It names the alternative (slowhop_place) and the exact condition for switching to it (need for description, units, house rules, or exact quote).

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