Skip to main content
Glama

Hold a time and email the client to confirm

hold_booking
Idempotent

Use this when the person has picked a time from check_availability and said yes to its price and the cancellation policy. Holds that time for up to 15 minutes and emails the person, who confirms it with the link in the email or by reading you the 6-digit code from it. Nothing is booked until they confirm. Pass the person's own name and email address, their time zone and an idempotencyKey: a retry with the same key and details returns the same hold. To change a time you already held, release the earlier hold with release_hold first. Do not use for holding a time for someone who has not given you their own email address, or for taking a payment.

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": {
      "slotId": "<slotId>",
      "client": "<client>",
      "clientTimeZone": "<clientTimeZone>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "hold_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes
slotIdYesA slotId from check_availability, used within 30 minutes.
languageNoThe language to answer in (BCP 47).
partySizeNo
clientTimeZoneYesThe client's IANA time zone, such as America/Toronto. Ask for their city when unsure.
idempotencyKeyYesThe same key and the same details for a retry of one hold; a new key for anything else.

Output Schema

NameRequiredDescriptionDefault
metaYes
holdIdYes
sentToYesThe address the email goes to, masked.
statusYes
bookingYes
demoCodeNoThe demo business only: the code to confirm with.
heldUntilNo
confirmWaysYes
bookingPageUrlYesThe business's own booking page, for when the email does not arrive.
demoConfirmUrlNoThe demo business only, for an example address that gets no email: the link the email would have carried. The person opens it to confirm.
messageForUserNo
nextStepIfNoEmailNoWhile the time is held for the person: what to do if they have no email after a few minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / booking / properties / freeCancellationPassed
      Added value: +{
      +  "description": "Only when the time to cancel for free had already passed when this was answered, in place of freeCancellationUntil: says so, in the answer's language.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / demoConfirmUrl
      Added value: +{
      +  "description": "The demo business only, for an example address that gets no email: the link the email would have carried. The person opens it to confirm.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, idempotent and open-world, but the description adds material behavior the agent cannot infer: a 15-minute expiry, an outbound email, two confirmation channels (link or 6-digit code), and that no booking exists until confirmation. Idempotency retry semantics ('same key and details returns the same hold') are spelled out concretely. The only gap is what happens after the 15-minute window lapses.

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 triggering condition before the mechanics, and each sentence carries a distinct rule. It is dense — several preconditions and exclusions are packed into long compound sentences — so it reads as slightly heavy, but nothing is wasted.

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 side-effecting tool with an output schema, this covers prerequisites, expiry, the confirmation handshake, idempotent retries, and the correct path for modifying a hold. Return values are handled by the output schema, so no explanation of the response shape is owed.

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?

Coverage is 67%, and the description compensates by explaining that client must be the person's own name and email, that the time zone belongs to that person, and that idempotencyKey must repeat for a retry but change for anything else — meaning beyond the schema's 'same key for a retry'. partySize and language are left entirely to the schema.

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 — holds a time for up to 15 minutes and emails the person to confirm — and explicitly separates itself from the booking step ('Nothing is booked until they confirm') and from a later time change (release_hold first). An agent can tell this apart from confirm_booking and release_hold without opening 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?

Gives a precise precondition (person picked a time from check_availability and accepted the price and cancellation policy), names the alternative for changing a held time (release_hold first), and states two explicit exclusions: no hold without the person's own email, and not for taking payment.

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