Skip to main content
Glama

Confirm Booking via Active Hold

create_booking
Idempotent
Finalize and confirm a reservation in the property's PMS using an active 15-minute hold (`hold_id`).
The property owner is the merchant of record with zero OTA intermediaries.

When to use:
    - Use after creating an active hold via `create_hold` to commit the reservation into the PMS (when `payment_required=False` or when authenticated with a tenant API key).
When NOT to use:
    - Do NOT call `create_booking` without first locking inventory via `create_hold`.
    - When `create_hold` returns `payment_required=True` on a public session, direct the guest to the `checkout_url` instead of calling `create_booking` before payment.

Args:
    hold_id:         Hold ID from create_hold (must be active, not expired)
    guest_name:      Full name of primary guest
    guest_email:     Guest email
    guest_phone:     Guest phone (international format, e.g. +306912345678)
    idempotency_key: Unique key from caller — prevents double-booking on retry
    notes:           Optional special requests

Returns:
    JSON object with `success`, `booking_id`, `pms_booking_id`, `unit_id`, `check_in`, `check_out`, `status`, and confirmation dispatch flags.

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": {
      "hold_id": "<hold_id>",
      "guest_name": "<guest_name>",
      "guest_email": "<guest_email>",
      "guest_phone": "<guest_phone>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional special requests, arrival notes, or flight details.
hold_idYesActive 15-minute inventory hold ID returned by `create_hold`.
guest_nameYesFull legal name of the lead guest.
guest_emailYesPrimary guest email address for confirmation and pre-arrival check-in.
guest_phoneYesGuest phone/WhatsApp number in international E.164 format (e.g. '+306912345678').
idempotency_keyYesCaller-generated unique key (UUID or string) to guarantee idempotency and prevent duplicate bookings on retry.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / guest_email / description
      Added value: +"Primary guest email address for confirmation and pre-arrival check-in."
    • addedInput schema / properties / guest_name / description
      Added value: +"Full legal name of the lead guest."
    • addedInput schema / properties / guest_phone / description
      Added value: +"Guest phone/WhatsApp number in international E.164 format (e.g. '+306912345678')."
    • addedInput schema / properties / hold_id / description
      Added value: +"Active 15-minute inventory hold ID returned by `create_hold`."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Caller-generated unique key (UUID or string) to guarantee idempotency and prevent duplicate bookings on retry."
    • addedInput schema / properties / notes / description
      Added value: +"Optional special requests, arrival notes, or flight details."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond `readOnlyHint=false` and `idempotentHint=true`, it discloses the 15-minute hold expiry constraint, the payment-gated branch that must be routed to checkout instead, and the merchant-of-record model. It also explains that the idempotency key exists to prevent double-booking on retry, giving the annotation operational meaning.

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 description is front-loaded with purpose, then structured into when/when-not and args. It is slightly padded by the Args and Returns sections that duplicate the 100%-covered schema and the existing output schema.

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 mutating booking tool with five required parameters, the description covers prerequisites, the payment-gated failure path, and retry semantics; the output schema already documents return values, so nothing an agent needs is missing.

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?

Schema description coverage is 100%, so the baseline is 3, and the Args block largely restates the schema (guest_phone international format, notes as optional special requests, idempotency_key as caller-generated unique key). The only genuine addition is that `hold_id` must be active and not expired.

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 first sentence gives a specific verb and resource ("Finalize and confirm a reservation in the property's PMS") and names the mechanism (an active 15-minute hold via `hold_id`), which immediately separates it from `create_hold` and `cancel_booking`.

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 has explicit "When to use" and "When NOT to use" blocks: only after `create_hold`, only when `payment_required=False` or with a tenant API key, and explicitly redirect to `checkout_url` when payment is required. The alternative path is named rather than implied.

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