Skip to main content
Glama

ATA Travel

by cloud.atatravel
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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
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. 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"
+]
  2. 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"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

It goes well beyond the annotations by explaining that policyAcknowledged is the binding consent flag, that identity verification is not consent, that host-approval enquiries may pass false because payment is not due, and that verification flows require keeping internal tool details private. It also discloses the resulting action: inventory-holding booking or enquiry hold, with next-step outcomes.

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 opening sentence is front-loaded with the tool's purpose, and each subsequent sentence adds a distinct compliance or branching detail. It is dense and could benefit from formatting, but there is no meaningful redundancy.

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 financially binding mutation with 19 parameters, no output schema, and openWorldHint true, the description covers the two booking modes, consent criteria, verification side effects, and next-step outcomes. It does not detail response fields or edge cases, but those are not required here given the absence of an output schema.

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 valuable parameter semantics for policyAcknowledged (true only after exact total, payment schedule, and cancellation terms are shown), guestCountry (required for bookings, optional for quotes), and the travelerAssertion-or-agentHandoffId requirement. However, with schema coverage around 47%, many parameters such as propertyToken, roomId, adults, internalAgentKey, and priceAudience receive no added explanation, so the description only partially compensates for the schema's gaps.

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 first sentence names a concrete action and result: 'Secure a reservation or create a host-approval enquiry on behalf of a traveler.' The branch details further clarify two distinct outcomes. It does not explicitly contrast this with the sibling create_quote, so it stops short of a 5.

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?

The description gives explicit conditions for instant booking ('If instant book is enabled and payment is ready') versus creating an enquiry hold ('If instant book is disabled or Stripe checkout is not ready'), plus consent and verification prerequisites. It does not name alternative tools or state when not to use this tool, so it lacks the full when-not/alternatives guidance of a 5.

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

All ATA Travel 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