Skip to main content
Glama

any.cab

Book a quoted transfer

create_booking
Idempotent

Book a quote for the passenger. Returns booking_id and a payment_url for the traveller; nothing is charged until they pay there, and the booking is confirmed only after payment. Retrying with the same idempotency_key returns the same 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>",
      "passenger": "<passenger>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoFor the driver, max 500 characters
quote_idYesquote_id from get_quote, unchanged
passengerYes
flight_numberNoFor airport pickups, e.g. FR1234
idempotency_keyNo8-100 characters; reuse it when retrying the same booking

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag idempotentHint=true and openWorldHint=true, but the description adds real context: no charge occurs until payment at the payment_url, and the booking is only confirmed after payment. The retry sentence restates the idempotency annotation with the concrete consequence (same key returns the same booking), which is useful but not new.

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?

Two sentences, no filler, and the lifecycle constraint (charge/confirm timing) is front-loaded right after the purpose and return values. Every clause carries distinct information.

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 carries the burden of describing returns, and it does name booking_id and payment_url. It covers the payment lifecycle and retry behavior, but is silent about quote expiry, error cases, or whether the payment_url is time-limited, which would matter for a booking flow.

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 80%, so the schema documents the fields, and the description adds semantics for only one of them (idempotency_key retry behavior) – the same information the annotation implies. It adds nothing about notes, passenger, or flight_number that the schema does not already carry.

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 quote for the passenger") and pins down the return values (booking_id, payment_url). An agent can distinguish it from the read-only siblings get_quote and get_booking purely from this sentence because it is the only one that creates a booking.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied: it takes a quote_id, so the flow is get_quote then create_booking, but the description never states that prerequisite or names when not to use it (e.g., for an unquoted or already-booked trip). The retry guidance is the only explicit conditional.

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