Skip to main content
Glama

create_provisional_booking

Secure a reservation or create a host-approval enquiry on behalf of a traveler. policyAcknowledged is required as an explicit boolean and must be true for financially binding flows after the exact total, payment schedule, and cancellation terms are shown; identity verification is not consent. A host-approval enquiry may pass false because payment is not due unless accepted. Also requires the traveler’s full name, email, and country (guestCountry, required for bookings; optional for quotes) plus travelerAssertion or approved internal BOOKING_HOLD agentHandoffId. If verification is needed, keep internal tool details private; tell the traveler to confirm their email and follow the code or link instructions returned by verification. If instant book is enabled and payment is ready, creates an inventory-holding provisional booking and returns payment/manual-payment next steps. If instant book is disabled or Stripe checkout is not ready, creates an enquiry hold for host approval/payment follow-up.

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": {
      "propertyToken": "<propertyToken>",
      "roomId": "<roomId>",
      "checkIn": "<checkIn>",
      "checkOut": "<checkOut>",
      "guestName": "<guestName>",
      "guestEmail": "<guestEmail>",
      "guestCountry": "<guestCountry>",
      "adults": "<adults>",
      "policyAcknowledged": "<policyAcknowledged>"
    },
    "name": "create_provisional_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional traveler comments, questions, or requests for the host. Especially useful for host-approval enquiries.
adultsYes
roomIdYes
checkInYes
checkOutYes
childrenNo
guestNameYesTraveler’s full name, as supplied by the traveler.
guestEmailYes
guestPhoneNo
ratePlanIdNoRate plan ID. If omitted, the system auto-selects the default active rate plan per night, then the cheapest active auto-selectable fallback.
guestCountryYesRequired traveler country, as supplied by the traveler. Ask only if missing. Do not infer it from the property location, language, currency, or phone number. Quotes do not require country.
priceAudienceNo
propertyTokenYes
agentHandoffIdNoApproved ATA traveler handoff ID from start_traveler_handoff/get_traveler_handoff_status. Required for third-party agents before inventory-holding booking actions.
displayCurrencyNoOptional 3-letter currency for approximate traveler-facing display conversion. Native property currency remains authoritative.
internalAgentKeyNo
bookingAssistanceNoInternal Little John booking attribution; requires the internal agent credential.
selectedRoomCountNoFor direct-booking room-count configurations, the number of rooms the traveler selected. Use defaultSelectedRoomCount from availability results.
travelerAssertionNoSigned traveler email verification assertion from ATA.
policyAcknowledgedYesExplicit policy-consent state. Set true only after the traveler agrees to the exact price, payment schedule, and cancellation terms. Required before creating either an instant-book hold or a host-approval enquiry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / guestEmail / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed1 schema field changed
    • addedInput schema / properties / bookingAssistance
      Added value: +{
      +  "description": "Internal Little John booking attribution; requires the internal agent credential.",
      +  "enum": [
      +    "AI_ASSIST"
      +  ],
      +  "type": "string"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / guestCountry
      Added value: +{
      +  "description": "Required traveler country, as supplied by the traveler. Ask only if missing. Do not infer it from the property location, language, currency, or phone number. Quotes do not require country.",
      +  "maxLength": 80,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / guestName / description
      Added value: +"Traveler’s full name, as supplied by the traveler."
    • addedInput schema / properties / guestName / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "propertyToken",
      -  "roomId",
      -  "checkIn",
      -  "checkOut",
      -  "guestName",
      -  "guestEmail",
      -  "adults",
      -  "policyAcknowledged"
      -]New value: +[
      +  "propertyToken",
      +  "roomId",
      +  "checkIn",
      +  "checkOut",
      +  "guestName",
      +  "guestEmail",
      +  "guestCountry",
      +  "adults",
      +  "policyAcknowledged"
      +]
  4. Changed2 schema fields changed
    • addedInput schema / properties / policyAcknowledged
      Added value: +{
      +  "description": "Explicit policy-consent state. Set true only after the traveler agrees to the exact price, payment schedule, and cancellation terms. Required before creating either an instant-book hold or a host-approval enquiry.",
      +  "type": "boolean"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "propertyToken",
      -  "roomId",
      -  "checkIn",
      -  "checkOut",
      -  "guestName",
      -  "guestEmail",
      -  "adults"
      -]New value: +[
      +  "propertyToken",
      +  "roomId",
      +  "checkIn",
      +  "checkOut",
      +  "guestName",
      +  "guestEmail",
      +  "adults",
      +  "policyAcknowledged"
      +]
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: consent must follow exact price/payment/cancellation terms, identity verification is not consent, host-approval enquiries may not require payment, and internal tool details should remain private during verification. It also states what the tool returns in each flow, which is substantial context for a write operation with no output schema.

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?

The purpose is front-loaded and the key consent and flow conditions follow in a logical order. It is dense and long, but most sentences carry useful decision or safety information for a complex booking tool.

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?

For a complex, non-idempotent write tool with no output schema, the description covers the main behavioral, consent, verification, and outcome branches well. It is still incomplete on several of the 20 parameters and does not fully describe return values beyond payment/manual-payment next steps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaningful semantics for policyAcknowledged, guestCountry, travelerAssertion, and agentHandoffId, including required versus optional contexts. However, with 20 parameters and only 50% schema description coverage, many parameters such as propertyToken, roomId, dates, adults, children, internalAgentKey, bookingAssistance, and selectedRoomCount are not clarified in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific dual purpose: securing a reservation or creating a host-approval enquiry on behalf of a traveler. It distinguishes the two outcomes clearly, but does not explicitly name create_quote as the alternative for quote-only flows, leaving some sibling differentiation implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear conditions for the two flows: instant book plus ready payment creates an inventory-holding provisional booking, while disabled instant book or unready Stripe checkout creates an enquiry hold. It also explains when policyAcknowledged may be false, but does not explicitly route quote use cases to create_quote or list when not to use this tool.

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