Skip to main content
Glama

Change a booking

modify_booking
Destructive

Change the slot or quantity (改時間、改人數) of a pending, awaiting_payment or confirmed booking, when the customer asks to. Replaces the booking's time or quantity and frees the old place. Use a slot value from get_availability. A booking paid online can change its slot but not its quantity (cancel and rebook instead). Changes close at the same cutoff as online cancellation.

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": {
      "business_id": "<business_id>",
      "booking_id": "<booking_id>",
      "status_token": "<status_token>"
    },
    "name": "modify_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
slotNoNew slot value from get_availability
quantityNoNew number of people or places
booking_idYesbooking_id returned by request_booking
business_idYesbusiness_id from search_businesses
status_tokenYesstatus_token returned once by request_booking
idempotency_keyNoOptional key (8–64 letters, digits, _ . : -) that makes retries safe: the same key with the same parameters returns the original result

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=false, so the description's added value is the domain behavior: the old place is freed, paid-online bookings are slot-only, and changes are gated by a cutoff. The cutoff is only defined by reference to "the same cutoff as online cancellation," which the agent cannot resolve from this definition, and no failure or rollback behavior is described for this destructive mutation.

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?

Dense and front-loaded: the eligible statuses and the mutation scope come first, then the cross-references and the payment restriction. The parenthetical Chinese gloss is mildly redundant for an English-reading agent, but no sentence is filler and the ordering matches how an agent would reason about the call.

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 destructive, non-idempotent mutation with six parameters and no output schema, the description covers eligibility, the alternative path, and the slot source — enough to call it correctly. What it omits is what the call returns after a successful change and how failures surface, which matters slightly more because there is no output schema to fall back on.

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 the baseline is 3, but the description adds real meaning beyond it: slot values must come from get_availability, and quantity is subject to a conditional restriction (not changeable for paid-online bookings) that the schema's "New number of people or places" does not convey. That constraint directly changes how an agent should populate the quantity parameter.

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 ("Change the slot or quantity ... of a booking") and immediately scopes it to the eligible statuses (pending, awaiting_payment, confirmed). It also names the sibling it is not — cancel_booking is implied by "cancel and rebook instead" — so an agent can distinguish it from cancel_booking, complete_booking and request_booking without opening any 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?

Gives explicit when-to-use ("when the customer asks to"), the status precondition, and a concrete exclusion with the correct alternative for paid-online bookings that want a quantity change. It also routes the agent to get_availability for valid slot values, which is a real cross-tool instruction rather than an implied one.

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.