Skip to main content
Glama

workspace

by be.florealholidays
OverviewDiscussionsAdmin

Price of a stay

get_stay_price
Read-onlyIdempotent

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.

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)
domainYesLocation slug from list_locations, e.g. "floreal-blankenberge"
nightsYesNumber of nights
arrivalYesArrival date (YYYY-MM-DD)
childrenNoNumber of children (under 12)
packageIdNoPackage id from list_arrangements (optional)
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • 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)"
    • changedInput schema / properties / domain / description
      Previous value: -"Location slug, e.g. \"floreal-blankenberge\""New value: +"Location slug from list_locations, e.g. \"floreal-blankenberge\""
    • 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"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive traits. The description adds valuable behavior beyond that: exact-date-full fallback to alternatives within three days, flexibleDays pricing around the arrival, and the mandatory instruction to share bookingUrl with the guest. No contradiction 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?

The description is compact, front-loaded with the core purpose, and then adds the few non-obvious behaviors in a logical sequence. Every sentence earns its place; there is no filler or restatement of schema details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 explains the key returned information: price, availability, accommodation kind, sleeping capacity, and bookingUrl, plus fallback alternatives. It does not enumerate every possible output field or edge case, but it supplies enough for an agent to invoke the tool and handle the result correctly.

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?

The schema already documents all 10 parameters with descriptions, so the baseline is 3. The description adds cross-tool semantics: packageId originates from list_arrangements, flexibleDays searches surrounding days, and the party concept aggregates adults/children/babies/pets. This meaningfully exceeds what the schema alone provides.

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 precise, specific scope: '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.' It names the output dimensions (kind, sleeping capacity, bookingUrl) and explicitly contrasts with search_stays, so an agent can distinguish it from 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?

Gives concrete when-to-use guidance: use search_stays when no location is chosen, pass a packageId from list_arrangements to price a specific package, and use flexibleDays for date-flexible searches. This is explicit routing to alternatives rather than leaving the decision to inference.

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