Skip to main content
Glama

Reserve a Quo ride

reserve_ride

Request a Quo captain reservation. No account or payment needed to request, a concierge confirms every ride by phone, text, or email before it's finalized, exactly like the public booking form. Nothing is charged by this call. If the guest has already linked a card with a spending cap (see get_payment_method), reserve_and_pay can also complete payment in the same call instead of just requesting.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "pickup": "<pickup>",
      "when": "<when>"
    },
    "name": "reserve_ride"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesGuest's full name
whenYesPickup date and time, ISO 8601 (e.g. 2026-12-04T14:30:00-05:00)
emailNo
hoursNo
notesNo
phoneYesGuest's mobile number, required, the concierge confirms by phone/text. Any common format is fine (e.g. "305-555-0100", "(305) 555-0100"); non-digit characters other than a leading + are stripped server-side.
stopsNoOrdered intermediate stops between pickup and dropoff within this one reservation (e.g. a hotel stop to grab a bag before continuing to the airport). Up to 3. Pricing here isn't distance-based, so each stop adds a flat surcharge to the fare, reflected in the confirmation.
pickupYesPickup address, airport, or hotel
dropoffNoDestination, omit for an hourly/as-directed booking
serviceNotransfer
vehicleNosedan
flightNumberNoFor an airport pickup, Quo tracks the flight and the captain waits if it's delayed
idempotency_keyNoOptional. A unique string for this reservation request (e.g. a UUID). If the call is retried with the same key, the original reservation is returned instead of creating a second ride.
specialRequestsNo
additionalRidersNoOther named riders on this same booking, for a group/split-fare trip, the caller above stays the sole booking owner (auth, cancel rights, and payment all stay with them). Purely for the driver's manifest and, if a phone is given, that rider's own SMS ride updates. Not a separate payment, the organizer's card is still charged the full fare.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare the mutation/open-world profile; the description adds real behavioral context — nothing is charged, no account needed, and a human concierge confirms by phone/text/email before the ride is finalized, so the agent understands the request is provisional. It does not cover retry behavior or what the call returns, which the idempotentHint=false annotation combined with an idempotency_key param makes worth stating.

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, front-loaded with the action and risk profile, then the alternative. The "exactly like the public booking form" clause earns its place by reinforcing the no-account guarantee.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter booking mutation with no output schema, the description explains the confirmation flow well but never says what the call returns (reservation id, pending status) or how the fare is presented, leaving the agent guessing at the response shape.

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 description coverage is 60% across 15 parameters, so the schema carries most semantics (stops, additionalRiders, when, phone are all documented there). The description adds little parameter-level meaning beyond the payment linkage, so baseline 3 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?

Opens with a specific verb+resource ("Request a Quo captain reservation") and immediately distinguishes the tool from its payment-capable sibling by describing itself as a request-only path with concierge confirmation.

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?

Gives explicit conditions: no account or payment required, and points to get_payment_method plus reserve_and_pay when a card with a spending cap is already linked. It stops short of advising whether to call get_quote first for pricing, so it is clear context rather than a full when/when-not rubric.

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