Skip to main content
Glama

Get a checkout link

book
Idempotent

Checks a quote_id is still available and returns a checkout_url for the traveler to open. The traveler signs in, reviews the price, house rules and cancellation policy, and pays there; this tool reserves nothing and charges nothing by itself. It accepts no card or payment details: a request containing them is refused.

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>"
    },
    "name": "book"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesThe quote_id from get_quote. Quotes last 15 minutes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only supply the generic safety flags (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true). The description adds real behavioral context beyond them: the expiry/availability check, that payment and review happen on the hosted page, that nothing is reserved or charged here, and that requests carrying card data are refused. That last refusal rule is especially valuable and appears nowhere in the structured fields.

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?

Three tight sentences: what it does, what happens downstream, what it refuses. The critical framing (reserves nothing, charges nothing) is front-loaded rather than buried, and no sentence is filler.

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?

With a single required parameter and no output schema, the description carries the return-value burden itself by naming checkout_url, and it also explains the human handoff step. Nothing an agent needs in order to call this 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%, and the schema already documents quote_id as coming from get_quote with a 15-minute lifetime. The description restates the availability check but adds no new syntax, format, or constraint detail, so the baseline 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?

The description opens with a specific verb and outcome: it validates the quote_id and returns a checkout_url. That is clearly distinct from the sibling read tools (get_quote, search_stays) and from find_cheaper, so an agent can select it 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: this is the step after get_quote that hands the traveler off to a paid checkout, and the description explicitly rules out treating it as a reservation or charge. It does not name a sibling alternative or state a when-not-to-use condition, so it falls just short of full routing guidance.

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