Skip to main content
Glama

Black Car Service — Bay Area Ride Quotes

Create a pending SUV reservation

book_ride
Destructive

After the customer explicitly confirms a quote_ride estimate and trip, create a pending reservation and return its secure website checkout link. Requires the exact signed booking_token from that quote plus customer-provided name, email and phone. Rechecks price and live availability. Does not hold a vehicle, confirm payment, charge a card, or enroll SMS. Reuse the SAME token and contact details on retries; uncertain outcomes must not be bypassed with a new token. Never request payment credentials.

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": {
      "booking_token": "<booking_token>",
      "customer_name": "<customer_name>",
      "customer_email": "<customer_email>",
      "customer_phone": "<customer_phone>",
      "customer_confirmed": "<customer_confirmed>"
    },
    "name": "book_ride"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_tokenYesExact booking_token returned by quote_ride. Reuse this token and the same contact details on every retry; never invent a token.
customer_nameYesName supplied by the customer for this reservation.
customer_emailYesCustomer-supplied email for booking communications.
customer_phoneYesCustomer-supplied contact phone. Does not enroll the customer in SMS.
customer_confirmedYesOnly true after the customer explicitly approves the quoted trip, total, and creation of a pending reservation. Payment requires separate customer approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / customer_email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed1 schema field changed
    • changedInput schema / properties / customer_confirmed / description
      Previous value: -"Only true after the customer explicitly approves the quoted trip, total, and creation of a pending reservation requiring secure website checkout."New value: +"Only true after the customer explicitly approves the quoted trip, total, and creation of a pending reservation. Payment requires separate customer approval."
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare the safety profile (destructive, non-idempotent, open-world); the description adds substantive behavior beyond them — live price/availability recheck, no vehicle hold, no payment or SMS side effects, and the critical retry semantics that constrain how an agent may re-invoke a non-idempotent call. It also restates the security boundary 'never request payment credentials'.

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?

Six short sentences, each carrying a distinct constraint: trigger, return value, required inputs, revalidation, explicit non-effects, retry rule, security rule. The precondition and result come first; no 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?

For a non-idempotent, destructive creation tool with no output schema, the description covers everything an agent needs: the precondition gate, the returned checkout link, which side effects do and do not occur, and the retry discipline. Nothing material is left to inference.

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 the baseline is 3; the description still adds value by tying booking_token to its origin in quote_ride and mandating that the same token and contact details be reused across retries — semantics the schema repeats but does not fully motivate. customer_confirmed's intent is reinforced but not extended much beyond the schema's const/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?

States a specific verb and resource — 'create a pending reservation and return its secure website checkout link' — with the triggering condition (customer-confirmed quote_ride estimate) front-loaded. This clearly separates it from quote_ride (estimate), complete_booking (payment/confirm) and get_booking_status (read).

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?

Explicit when-to-use ('After the customer explicitly confirms a quote_ride estimate and trip'), explicit when-not ('does not hold a vehicle, confirm payment, charge a card, or enroll SMS'), and explicit retry policy (reuse the same token and contacts; do not bypass uncertain outcomes with a new token). No alternatives need to be inferred.

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