net.praegant/landhaus

Tools

• check_availability

  Check live availability and exact prices at Landhaus Apartments Prägant for concrete dates and a party. Use this whenever a guest names dates — it is the main tool. It applies the booking rules (arrival days, minimum stay, closures), recommends the apartment that suits the party best (with reasons, e.g. 2 separate bedrooms for families) and lists the free apartments with the total split into stay, final cleaning and tourist tax, the payment and cancellation terms, the website offers valid for the stay and a pre-filled booking link per apartment. If the wish is not bookable it returns the nearest bookable alternative dates with prices instead; parties larger than one apartment get a combination of apartments. Ask for dates, number of adults and the ages of all children first — never assume them. Not for: prices of a whole month without dates (get_rates), apartment descriptions (get_apartment_details). To show the result visually, call render_availability_card with the same arguments. Behaviour: read-only, nothing is booked or reserved, no personal data. Live from the property's booking system (typically 1-2 s, identical requests cached 90 s). Invalid input returns isError with the reason. Returns a text summary plus structuredContent (status, apartments with breakdown and booking_url, alternatives, group, terms, offers, inquiry_url).

  shallow
• get_apartment_details

  Describe one or all apartments: size, bedrooms, maximum guests, description and page link. Use for questions about the apartments themselves ("how big is #16?", "which apartment has 2 bedrooms?", "which apartments fit 5 people?"). It contains no prices or availability — use check_availability for dates and prices, or get_rates for a month overview. Studio #17 is only listed when asked for by number and is marked as bookable on request. Visual version with photos: render_apartment_gallery. Behaviour: read-only; facts as maintained on praegant.net (synced hourly), answers in milliseconds. Returns text plus structuredContent.apartments (nr, name, m2, bedrooms, max_guests, description, url, on_request, images). An unknown number returns the list of existing apartment numbers.

  shallow
• get_booking_link

  Build a direct booking link on praegant.net, optionally pre-filled with dates, party and apartment. Use when the guest has decided and just wants the link, or wants to book without a price check. Bookings are always completed by the guest on praegant.net (no commission) — this connector never books, reserves or takes payment by design. check_availability already returns a booking link per free apartment, so call this only when no availability result is at hand. Dates are optional (YYYY-MM-DD); without them the link opens the booking page. Behaviour: read-only, no availability check, instant. Returns text plus structuredContent (booking_url, inquiry_url, phone, email).

  shallow
• get_offers

  List all current seasonal offers and packages published on praegant.net. Use when the guest asks about deals, packages or what is special in a season, independent of dates. When the guest already has dates, check_availability includes only the offers valid for that stay — no need to call both. Visual version: render_offers_card. Behaviour: read-only; offers as published on the website (synced hourly, expired ones removed). Returns text plus structuredContent.offers (title, valid_from, valid_to, price_text, summary, url).

  shallow
• get_rates

  Get the price level of each apartment for a whole month plus that month's booking rules. Use when the guest has no exact dates yet ("what does a week in July cost?", "when is it cheapest?"). For each apartment it returns the lowest total price of a real reference stay in that month (usually 7 nights, incl. final cleaning and tourist tax) and the arrival days / minimum stay / closures of the month. Not for exact prices on specific dates — use check_availability for that. Visual version: render_rates_card with the same arguments. Behaviour: read-only, live from the booking system (about 1-2 s, cached 5 min). Returns text plus structuredContent (apartments, periods, weeks, perks, offers).

  shallow
• get_region_info

  Return curated information about Bad Kleinkirchheim and the house for a topic. Use for "what can we do there?" and house questions: house rules and services (self-catering, no breakfast, bread-roll service, no pets, baby cot/high chair on request, chip access), skiing (winter), hiking, biking and lakes (summer), thermal spas and the in-house sauna (wellness), golf incl. the free green fee and tee-time booking, families, workation, arrival. The Kärnten Card (summer only) and the free green fee are explained exactly. Not for prices or availability (check_availability) and not for apartment facts (get_apartment_details). Behaviour: read-only, static curated content from the property (no web search), instant. Returns text plus structuredContent.topics (topic, lines) and contact details.

  shallow
• render_apartment_gallery

  Show one or all apartments with photos as an interactive gallery card in the chat. Use instead of get_apartment_details when the guest wants to see the apartments (one apartment: up to 3 swipeable photos; all: one photo each, with buttons to check availability or open the page). Same arguments, behaviour (read-only, no prices) and result as get_apartment_details, plus photos.

  shallow
• render_availability_card

  Show the availability result for given dates and party as an interactive card in the chat. Use after check_availability (or instead of it) when the guest wants to SEE the options: photos, total price with an expandable breakdown, a booking button per apartment, tappable alternative dates. Use check_availability alone when only reasoning over the data or when the client cannot display cards. Behaviour and arguments are identical to check_availability (read-only, live, nothing booked); the result additionally contains small photos and the Google rating. Returns the same text and structuredContent.

  shallow
• render_offers_card

  Show the current website offers as an interactive card with photos and links. Use instead of get_offers when the guest wants to browse the offers visually. Same behaviour (read-only) and result as get_offers, plus a photo per offer.

  shallow
• render_rates_card

  Show a month's prices and booking rules as an interactive card in the chat. Use instead of get_rates when the guest wants to see the overview; each apartment line can be tapped to check its dates. Use get_rates when only the data is needed. Same arguments, behaviour (read-only, live) and result as get_rates.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/c3222c29-12bd-4bcc-b029-1768f658c19a/badge.svg)](https://vouch.tools/servers/c3222c29-12bd-4bcc-b029-1768f658c19a)