Skip to main content
Glama

Book now: hold dates with the host

book_stay

Holds dates for the traveller at a home whose host offers "Book now" on CielStay (bookNow.available in get_listing_details): a Pro host whose calendar CielStay keeps in sync, within the host's limits (nights, lead time, guests, pets). guestEmail must be the traveller's own address: CielStay emails it a confirmation link, and the booking holds the dates for 30 minutes until the traveller confirms. On confirmation the dates are blocked on the host's calendar and the traveller receives the host's payment instructions. The booking and the payment are between the traveller and the host: CielStay is not a party to it and takes no payment. status "awaiting_guest_confirmation" on success; otherwise error explains why (dates taken, over the host's limits, calendar not confirmable just now) and contact_host remains available for a request instead. The reply's next describes what the traveller receives.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listingId": "<listingId>",
      "guestEmail": "<guestEmail>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>"
    },
    "name": "book_stay"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe traveller's name, as the host will see it
petsNoNumber of pets
guestsNoNumber of guests
checkInYesArrival date, YYYY-MM-DD
messageNoA note to the host from the traveller (arrival time, who is coming)
checkOutYesDeparture date, YYYY-MM-DD
listingIdYesThe home's CielStay id (or slug)
guestEmailYesThe traveller's own email address: the confirmation link and the host's payment instructions go there

Output Schema

NameRequiredDescriptionDefault
nextNo
errorNo
totalNo
statusNo
messageNo
successNo
expiresAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: a 30-minute hold, an emailed confirmation link, calendar blocking only after guest confirmation, and payment instructions sent post-confirmation. It also discloses the commercial framing (CielStay is not a party and takes no payment), the success status value, and the failure modes. This is exactly the context the readOnlyHint/destructiveHint flags cannot convey.

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

Conciseness4/5

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

Single dense paragraph, front-loaded with the action and eligibility condition, and every sentence contributes operational detail. It is longer than typical but carries no filler; breaking the lifecycle/error content into separate sentences would aid scanning.

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?

For a non-idempotent, open-world mutation with 8 parameters, the description covers eligibility, the confirmation lifecycle, side effects, failure handling and the alternative path. Return values are covered by the output schema, and the description still summarises the status field for orientation.

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?

Schema coverage is 100%, so baseline is 3; the description lifts this by tying the parameters to host-imposed limits (nights, lead time, guests, pets) that explain why values may be rejected. The guestEmail guidance largely restates the schema wording, which keeps it from a 5.

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?

Names a specific verb and resource ('Holds dates for the traveller at a home') and immediately scopes it to hosts offering 'Book now' (bookNow.available in get_listing_details). It is clearly distinguishable from contact_host, which the description explicitly positions as the fallback request path.

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?

States the preconditions for use (Pro host, calendar CielStay keeps in sync, within the host's limits on nights, lead time, guests, pets) and names the alternative explicitly: on error, contact_host remains available for a request instead. Both when-to-use and when-not-to-use are covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources