Skip to main content
Glama

Confirm a held time with the client's code

confirm_booking
Idempotent

Use this when the person reads you the 6-digit code from the email hold_booking sent them. Books the held time: the answer is confirmed, or requested when the business looks at new bookings before accepting them, with the booking's reference. If someone else took the time first, it offers up to three other times. A wrong code is refused and says how many tries are left. Do not use for a code the person did not give you themselves, or to try codes.

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": {
      "holdId": "<holdId>",
      "code": "<code>"
    },
    "name": "confirm_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe 6-digit code from the email, as the person read it to you.
holdIdYesThe holdId hold_booking answered with.
languageNoThe language to answer in (BCP 47).

Output Schema

NameRequiredDescriptionDefault
refNoThe booking's reference, for the person to quote to the business.
metaYes
statusYes
bookingNo
nextStepYesWhat to tell the person next.
alternativesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the possible outcomes: confirmed, or 'requested' when the business reviews new bookings, with a booking reference returned. It also covers the conflict path (up to three alternative times offered) and the failure path (wrong code refused, remaining attempts reported), which an agent cannot infer from readOnlyHint/idempotentHint alone.

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-loads the trigger condition and then layers outcomes, conflict handling, and prohibitions with no filler. The middle sentence packing three outcomes into one clause chain is slightly dense but every sentence carries actionable information.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the meaningful outcomes and the booking reference. For a 3-parameter confirmation tool with open-world behavior, nothing an agent needs in order to call it correctly 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 coverage is 100%, so the schema already documents all three parameters, establishing a baseline of 3. The description adds a little provenance — that the code comes from the email hold_booking sent and is read aloud by the person — but says nothing about the language parameter or format constraints beyond what the schema states.

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 ('Books the held time') plus the trigger condition (the person reads the 6-digit code from the hold email). This is clearly distinguishable from hold_booking (which creates the hold) and confirm_enquiry (a different confirmation flow).

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 an explicit when-to-use condition ('when the person reads you the 6-digit code from the email hold_booking sent them') and explicit when-not conditions ('Do not use for a code the person did not give you themselves, or to try codes'). Nothing about selecting this tool is left to inference.

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