Skip to main content
Glama

Book an activity

create_booking
Idempotent

Book a quoted activity for the signed-in client. Only call this after the user has seen the quoted total and explicitly agreed. Pass the quote_id, confirm_total_cents equal to the quote's total_cents, and a unique idempotency_key (reuse the same key when retrying). Nothing is charged here. The booking is held, not confirmed, and the reply says how to pay: a secure opas.world payment link, or in assistants that support in-chat payment, the payment handler details to pass to pay_for_booking.

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": {
      "quote_id": "<quote_id>",
      "confirm_total_cents": "<confirm_total_cents>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNo
quote_idYes
last_nameNo
first_nameNo
idempotency_keyYes
other_participantsNoEveryone else in the party, with name and email.
confirm_total_centsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that no charge occurs, that the result is a held (not confirmed) booking, and what the reply contains. It also explains idempotency semantics in practice — reuse the same key on retry — which the idempotentHint flag alone does not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four front-loaded sentences with no filler: purpose and actor first, then the consent precondition, then required parameters, then what happens after the call. Each sentence carries information an agent needs to invoke the tool correctly.

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?

With no output schema, the description still characterizes the response (held booking plus payment instructions), covering the most important unknown for a mutation tool with openWorldHint. It omits failure modes — e.g., behavior when confirm_total_cents mismatches the quote or the quote has expired — which would matter for a pricing-sensitive booking call.

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 description coverage is only 14%, so the description must compensate; it does so for all three required parameters, defining quote_id, the confirm_total_cents invariant against the quote total, and the uniqueness/reuse rule for idempotency_key. It says nothing about the optional first_name, last_name, phone, or other_participants fields, though those are largely self-describing.

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 ('Book a quoted activity') plus the acting scope ('for the signed-in client'), which separates it cleanly from get_my_booking, cancel_my_booking, and request_booking_change. The reference to a quoted activity also links it to the get_quote sibling without ambiguity.

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 precondition ('Only call this after the user has seen the quoted total and explicitly agreed') rather than leaving timing to inference. It also names the downstream alternative: use pay_for_booking when in-chat payment is supported, otherwise hand back the opas.world link.

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