Skip to main content
Glama

workspace

by be.florealholidays
OverviewDiscussionsAdmin

Search stays across all locations

search_stays
Read-onlyIdempotent

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoLanguage for accommodation names; defaults to Dutch, the language they are maintained in
petsNoNumber of pets
adultsYesNumber of adults
babiesNoNumber of babies (under 2)
nightsYesNumber of nights
regionNoRegion to limit the search to: coast, ardennes, kempen, gaume, wallonie-picarde (Dutch/French names work too)
arrivalYesArrival date (YYYY-MM-DD)
domainsNoLocation slugs to limit the search to; takes precedence over region
childrenNoNumber of children (under 12)
maxPriceNoHighest acceptable all-in price for the whole stay, in euro
flexibleDaysNoAlso 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.
accommodationNoAccommodation kind (hotel_room, studio, apartment, chalet, mobile_home, glamping, camping_pitch) or a word from the type name, e.g. "hotel", "apartment", "chalet", "tent"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / accommodation / description
      Previous value: -"Part of the accommodation name, e.g. \"hotel\", \"studio\", \"apartment\""New value: +"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\""
    • changedInput schema / properties / babies / description
      Previous value: -"Number of babies"New value: +"Number of babies (under 2)"
    • changedInput schema / properties / children / description
      Previous value: -"Number of children"New value: +"Number of children (under 12)"
    • addedInput schema / properties / flexibleDays
      Added value: +{
+  "description": "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.",
+  "maximum": 14,
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Language for accommodation names; defaults to Dutch, the language they are maintained in",
+  "enum": [
+    "nl",
+    "fr",
+    "en"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / region / description
      Previous value: -"Region to limit the search to: coast, ardennes, kempen, gaume, wallonie-picarde"New value: +"Region to limit the search to: coast, ardennes, kempen, gaume, wallonie-picarde (Dutch/French names work too)"
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark the tool read-only, idempotent, open-world, and non-destructive, and the description adds substantial behaviors beyond that: results are sorted cheapest first, one option per accommodation type, each result carries a bookingUrl that should always be shared, and when nothing matches the tool returns 'alternatives' within three days. It also clarifies that flexibleDays is a separate widening mechanism on top of the automatic three-day fallback. No contradiction exists with annotations.

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

Conciseness5/5

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

Every sentence earns its place: purpose is front-loaded, usage examples appear immediately after, then filters, result behavior, fallback behavior, and sibling routing. It is dense but not redundant, and the structure follows the natural decision flow an agent needs.

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?

With no output schema, the description must convey what the agent can expect from results, and it does: cheapest-first sorting, one cheapest option per accommodation type, bookingUrl on each result, and alternatives when nothing matches. Combined with annotations covering safety and idempotence, the definition gives an agent everything needed to select and invoke the tool correctly in the intended scenarios.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes well beyond the schema by giving practical meaning to several parameters: region's accepted values, accommodation's enum values plus natural-language equivalents like 'hotel' or 'chalet', maxPrice as the whole-stay all-in euro price, and flexibleDays as a same-call widening mechanism with an automatic three-day fallback. This meaningfully improves an agent's ability to map user requests to parameters.

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?

The description opens with a specific verb and resource: 'Find where Floreal Holidays has a stay available, across every location in one call, with the live all-in price per accommodation type.' It clearly distinguishes this tool from get_stay_price by framing it as the location-agnostic search, so an agent immediately knows what it does and how it differs from its siblings.

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?

It explicitly states when to use the tool: 'Use this whenever the guest has not picked a location yet,' and gives concrete guest-language examples. It also names the alternative for the known-location case ('For one known location get_stay_price gives the full picture'), and explains when to narrow with region, accommodation, maxPrice, and when to widen with flexibleDays. This is complete decision guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All workspace toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources