Skip to main content
Glama

Create 15-Minute Inventory Hold & Stripe Checkout

create_hold
Place an exclusive 15-minute inventory hold on a villa (`unit_id`) and generate a direct Stripe Checkout URL.

Locks the property's calendar for 15 minutes so no conflicting booking can occur while the guest completes payment.

When to use:
    - Use when the guest is ready to lock a specific `unit_id` and dates after reviewing `search_properties` or `get_rate_details`.
    - Always call `create_hold` before calling `create_booking`.
When NOT to use:
    - Do NOT use while browsing or comparing properties—use `search_properties` or `get_rate_details` instead.
    - If the guest decides not to proceed after a hold is created, call `cancel_hold` (not `cancel_booking`) to release the hold.

Args:
    unit_id:     The unit_id returned by search_properties
    check_in:    Arrival date YYYY-MM-DD
    check_out:   Departure date YYYY-MM-DD
    guests:      Number of guests
    guest_email: Primary guest email address to bind the reservation hold

Returns:
    JSON object with `hold_id`, `expires_at` timestamp, `payment_required` flag, `next_step`, and direct Stripe `checkout_url`.

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": {
      "unit_id": "<unit_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "guests": "<guests>",
      "guest_email": "<guest_email>"
    },
    "name": "create_hold"
  }
}

Input Schema

NameRequiredDescriptionDefault
guestsYesTotal number of guests staying at the property.
unit_idYesUnique property unit identifier (`unit_id` returned by `search_properties`).
check_inYesArrival date in ISO 8601 format (YYYY-MM-DD).
check_outYesDeparture date in ISO 8601 format (YYYY-MM-DD).
guest_emailYesPrimary guest email address to bind the 15-minute inventory hold and payment receipt.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / check_in / description
      Added value: +"Arrival date in ISO 8601 format (YYYY-MM-DD)."
    • addedInput schema / properties / check_out / description
      Added value: +"Departure date in ISO 8601 format (YYYY-MM-DD)."
    • addedInput schema / properties / guest_email / description
      Added value: +"Primary guest email address to bind the 15-minute inventory hold and payment receipt."
    • addedInput schema / properties / guests / description
      Added value: +"Total number of guests staying at the property."
    • addedInput schema / properties / unit_id / description
      Added value: +"Unique property unit identifier (`unit_id` returned by `search_properties`)."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and idempotentHint=false; the description adds the meaningful behavior — exclusive calendar lock, 15-minute expiry, conflicting bookings blocked, and a payment URL returned. It stops short of saying what happens at expiry or whether a second call creates a duplicate hold, which matters given idempotentHint=false.

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?

Front-loaded with the core action and effect, then cleanly sectioned into usage, args, and returns. The Returns block duplicates the existing output schema and the Args block duplicates the schema descriptions, which is wasted space, but the structure is easy to scan.

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 mutating, non-idempotent tool the description covers purpose, sequencing (hold before booking), and the cancellation path, and an output schema already explains return values. The remaining gap is post-expiry behavior and duplicate-hold risk, which an agent would want to know before retrying.

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 every parameter is already documented. The Args block largely restates the schema; the only added nuance is that guest_email binds the hold and receives the receipt, and that unit_id comes from search_properties. That is incremental value over a fully covered schema, so baseline 3 applies.

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?

States a specific verb and resource — place an exclusive 15-minute inventory hold on a villa identified by unit_id — plus the second effect (generating a direct Stripe Checkout URL). That two-part outcome distinguishes it clearly from create_booking and cancel_hold without needing to open either schema.

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?

Provides explicit when-to-use conditions (guest ready to lock a unit after reviewing search_properties or get_rate_details) and explicit when-not-to-use conditions (browsing/comparing). It also names the correct alternatives in both directions: search_properties/get_rate_details for browsing and cancel_hold rather than cancel_booking for releasing a hold.

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