workspace

Reviewed Jan 1, 2000.

• tools: 16 tools scanned
• metadata: scanned

No findings.

Tools (16)

• list_locations

  All Floreal Holidays locations in Belgium with their slug, name, kind of site, town, region and coordinates. Use the "slug" as the `domain` argument of every other tool. The "type" is the kind of site, not the accommodation on it — a park can offer hotel rooms, studios, apartments, chalets and camping pitches at the same time; ask list_accommodation_types for that. Locations with bookable=false (the head office) cannot be priced.

• search_stays

  Find where Floreal Holidays has a stay available, across every location in one call, with the live all-in price per accommodation type. Use this whenever the guest has not picked a location yet — "somewhere at the Belgian coast in July", "a hotel room in the Ardennes with a dog", "the cheapest week for a family of four". Narrow with `region` (coast, ardennes, kempen, gaume, wallonie-picarde), with `accommodation` (hotel_room, studio, apartment, chalet, mobile_home, glamping, camping_pitch, or plain words like "hotel", "appartement", "chalet") or with `maxPrice`; widen with `flexibleDays`. Results are sorted cheapest first, one cheapest option per accommodation type, and each result carries a bookingUrl for that location — always share it so the guest can book. When nothing matches, the answer lists "alternatives" within three days. For one known location get_stay_price gives the full picture.

• get_stay_price

  Live all-in price and availability for a stay at one Floreal location, per accommodation type, for the given arrival date, number of nights and party. Each option carries its kind (hotel room, studio, apartment, chalet, glamping, camping pitch) and how many people it sleeps. Pass a packageId from list_arrangements to price that specific package. With flexibleDays the same call also prices the days around the arrival; when the exact date is full the answer already lists "alternatives" within three days. The answer carries a bookingUrl: the same search on our own booking site — always share it so the guest can book. When the guest has not chosen a location yet, use search_stays instead.

• list_accommodation_types

  What kinds of accommodation one Floreal Holidays location offers — hotel rooms, studios, apartments, chalets, glamping, camping pitches — each with how many people it sleeps and an indicative "from" price. Use this for questions about what a location has ("does Blankenberge have hotel rooms?", "are there apartments in Nieuwpoort?"). A location can combine several kinds. Without a date it probes the next two months and every length of stay up to a week, so it also finds types that need a fixed number of nights. The prices are samples; ask get_stay_price for the guest's own dates.

• list_arrangements

  The bookable packages of one location: stay arrangements and add-on extras, with name, description and validity period. A package price depends on the stay and the party, so ask for it with get_stay_price and the packageId from this list.

• get_menu

  The current restaurant and food & beverage menus of one Floreal location, as published by that location. Not every location publishes menus.

• get_faq

  Published questions and answers about Floreal Holidays, optionally narrowed to one location. Answers are multilingual (Dutch, French, English).

• gift_card_info

  Information about Floreal Holidays gift cards: amounts, languages and where to buy one. Gift cards are valid at every location.

• whoami

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns who you are and which locations you may look at. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• flash_dashboard

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns occupancy, revenue and KPIs per day, month or year. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• arrivals

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns the reservations arriving on a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• departures

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns the reservations departing on a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• bookings_search

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns reservations in a date window, by room or booking number. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• reservation_detail

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns one reservation: dates, party size, room, status. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• day_summary

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns arrivals, departures and guests in house for a day. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.

• tasks_overview

  Needs a Floreal Workspace sign-in, which this connection does not have. Signed in it returns tasks per department and status. Call it anyway when the user asks for this: it answers with what is wrong and how to fix it, which is what they need to hear.