Skip to main content
Glama

booking

by com.mydriverparis

book_ride

Create a secure payment link to book a private chauffeur transfer. The reservation is created automatically ONLY after the customer completes payment. REQUIRED: call get_quote first and pass the resulting quote_id + the chosen vehicle_id. The price is taken from the stored quote (not from any price field you pass). Pass idempotency_key to make retries safe: the same key returns the same payment link instead of creating a duplicate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bagsNoNumber of bags
channelNoCaller channel identifier for observability. If omitted, the channel stored with the quote (from get_quote) is used.
quote_idYesquote_id returned by get_quote. Must be passed. Expired quote (>15 min) requires a fresh get_quote.
passengersNoNumber of passengers
vehicle_idYesVehicle ID chosen from the get_quote results
flight_numberNoFlight number for airport pickups (e.g. AF123)
passenger_nameYesFull name of the passenger
idempotency_keyNoOptional agent-generated key (e.g. UUID) to deduplicate retries. Same key + same params returns the same payment link for 24 h. Same key + different params returns an IDEMPOTENCY_CONFLICT error.
passenger_emailYesPassenger email for booking confirmation
passenger_phoneYesPassenger phone with country code (e.g. +33612345678)

TDQS

A4.6/5.0
Behavior5/5

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

The description discloses critical behavioral details beyond annotations: reservation is gated on payment completion, price is taken from the stored quote rather than passed value, and same idempotency_key returns the same payment link to prevent duplicates. These are not visible in the readOnlyHint/openWorldHint/idempotentHint annotations.

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?

The description is three sentences, each earning its place: purpose, prerequisite workflow, and idempotency guidance. It is front-loaded with the core action and avoids redundancy with the schema.

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?

For a complex tool with 10 parameters and no output schema, the description covers the essential workflow, payment semantics, and idempotency. It does not describe the return value format, but since no output schema exists and the description otherwise covers decision-relevant behavior, it is sufficiently complete.

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 coverage is 100%, so baseline is 3. The description adds meaningful context by explaining that quote_id must come from a prior get_quote call, vehicle_id is chosen from quote results, and price is derived from the quote. It also clarifies idempotency_key behavior beyond the schema's already detailed description.

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 begins with a specific verb and resource: 'Create a secure payment link to book a private chauffeur transfer.' This clearly distinguishes it from sibling tools like get_quote, get_vehicles, and book_meetgreet.

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?

It gives an explicit required workflow: 'REQUIRED: call get_quote first and pass the resulting quote_id + the chosen vehicle_id.' It also explains that the reservation is created only after payment, and mentions idempotency for retries. However, it does not explicitly state when NOT to use this tool or mention alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All booking toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: booking a ride, booking a meet & greet, getting a quote, listing vehicles, resolving flights/trains/locations, sending contact, etc. No two tools overlap in purpose or could be easily confused.

Naming Consistency5/5

All tool names follow a consistent lowercase snake_case verb_noun pattern, with verbs like 'book_', 'get_', 'resolve_', and 'send_' clearly indicating the action. There are no exceptions or mixed conventions.

Tool Count5/5

10 tools is well within the ideal 3-15 range and perfectly scoped for a chauffeur booking service. Each tool covers a necessary part of the workflow (quote, booking, location/flight/train resolution, vehicle info, policy, contact).

Completeness4/5

The core booking flow is well covered: resolve location/flight/train → get quote → book ride or meet & greet → send driver contact. However, there is no tool to cancel, update, or check the status of a booking, which requires external (Zeplan) access. This is a minor gap but workable for typical agent flows.

Resources