be.florealholidays/workspace

Measured conclusion: Alive, not deep-tested. L2 outcome: not_attempted.

Floreal Holidays Belgium: live prices and availability; staff run M&E dossiers, day sheets, tasks.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "workspace": {
      "url": "https://mcp.florealholidays.be/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (16)

• list_locations read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• search_stays read-only

  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.

  Parameters:

  • arrival (required) — string — Arrival date (YYYY-MM-DD)
  • nights (required) — integer — Number of nights
  • adults (required) — integer — Number of adults
  • lang — string — Language for accommodation names; defaults to Dutch, the language they are maintained in
  • pets — integer — Number of pets
  • babies — integer — Number of babies (under 2)
  • region — string — Region to limit the search to: coast, ardennes, kempen, gaume, wallonie-picarde (Dutch/French names work too)
  • domains — array — Location slugs to limit the search to; takes precedence over region
  • children — integer — Number of children (under 12)
  • maxPrice — number — Highest acceptable all-in price for the whole stay, in euro
  • flexibleDays — integer — Also search this many days before and after the arrival date, in the same call (0 = that day only). Use it for "around the 12th" or "some weekend in July". When the exact date has nothing, the tool already looks 3 days around it by itself.
  • accommodation — string — Accommodation kind (hotel_room, studio, apartment, chalet, mobile_home, glamping, camping_pitch) or a word from the type name, e.g. "hotel", "apartment", "chalet", "tent"

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_stay_price read-only

  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.

  Parameters:

  • domain (required) — string — Location slug from list_locations, e.g. "floreal-blankenberge"
  • arrival (required) — string — Arrival date (YYYY-MM-DD)
  • nights (required) — integer — Number of nights
  • adults (required) — integer — Number of adults
  • lang — string — Language for accommodation names; defaults to Dutch, the language they are maintained in
  • pets — integer — Number of pets
  • babies — integer — Number of babies (under 2)
  • children — integer — Number of children (under 12)
  • packageId — string — Package id from list_arrangements (optional)
  • flexibleDays — integer — Also search this many days before and after the arrival date, in the same call (0 = that day only). Use it for "around the 12th" or "some weekend in July". When the exact date has nothing, the tool already looks 3 days around it by itself.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_accommodation_types read-only

  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.

  Parameters:

  • domain (required) — string — Location slug from list_locations, e.g. "floreal-blankenberge"
  • lang — string — Language for accommodation names; defaults to Dutch, the language they are maintained in
  • arrival — string — Optional sample arrival date; omit to probe the next two months (YYYY-MM-DD)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• list_arrangements read-only

  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.

  Parameters:

  • domain (required) — string — Location slug, e.g. "floreal-blankenberge"

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_menu read-only

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

  Parameters:

  • domain (required) — string — Location slug, e.g. "floreal-blankenberge" (see list_locations)
  • lang — string — Menu language (defaults to Dutch)

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• get_faq read-only

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

  Parameters:

  • domain — string — Location slug; omit for the general questions

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• gift_card_info read-only

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

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• whoami read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• flash_dashboard read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• arrivals read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• departures read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• bookings_search read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• reservation_detail read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• day_summary read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

• tasks_overview read-only

  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.

  Hints: read-only yes · destructive no · idempotent yes · open-world yes

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.