Skip to main content
Glama

Miami Black SUV

Submit a confirmed booking

create_booking
Idempotent

Submit a trip the user confirmed. Return a hosted payment link for the confirmed deposit or full fare. A deposit saves the card for the automatic balance charge. Payment reserves the ride, subject to availability. Sprinter hourly and one-way are requests. For a payable trip, pass the same trip fields you sent to get_quote, plus fare_cents, stage and due_now_cents exactly as get_quote returned them.

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>",
      "email": "<email>",
      "phone": "<phone>",
      "idempotency_key": "<idempotency_key>",
      "user_confirmed": "<user_confirmed>"
    },
    "name": "create_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoDrop-off location ID, or other for a typed address.
bagsNoTotal bags. Defaults to zero.
dateNoPickup date in Miami, YYYY-MM-DD. For packages use legs.
fromNoPickup location ID, or other for a typed address.
langNoLanguage for booking email copy. Defaults to en.
legsNoPickup dates and times in the cruise package's leg order.
nameYesPassenger name confirmed by the user.
shipNoCruise ship name.
timeNoPickup time in Miami, HH:MM in 24-hour time. For packages use legs.
emailYesBooking email provided and confirmed by the user.
hoursNoChoose a whole number of hours from 2 to 12 for Suburban hourly and 3 to 12 for Sprinter hourly.
notesNoTrip notes the user wants to pass to Miami Black SUV.
phoneYesBooking phone number with country code where applicable.
stageNoPayment stage the user confirmed from get_quote. Required for payable trips. Use the stage value from get_quote.
flightNoArrival flight number for an airport pickup.
toTextNoDrop-off address when to is other, or stops for hourly Sprinter.
airlineNoAirline for the arrival flight.
escaladeNoRequest the Cadillac Escalade upgrade where offered, subject to availability.
fromTextNoPickup address when from is other.
languageNoPreferred language for communication.
occasionNoOccasion for the trip.
hotelTextNoHotel name or address for a cruise package with a hotel stop.
packageIdNoCruise package ID from get_service_info.
childSeatsNoPaid child seats by type.
fare_centsNoExact fare in cents the user confirmed from get_quote. Required for payable trips. Use the fare_cents value from get_quote.
passengersNoPassenger count, including children. Defaults to one.
returnTripNoReturn leg for a point-to-point round trip.
quote_centsNoExact request estimate in cents the user confirmed from get_quote. Required for request_estimate trips.
serviceTypeNoService type. Omit for point-to-point.
meetAndGreetNoRequest paid baggage-claim meet and greet for an airport pickup. Requires its flight number.
sprinterModeNoSprinter request mode. Omit for hourly.
due_now_centsNoExact amount due now in cents the user confirmed. Required for payable trips. Use the due_now_cents value from get_quote.
flightUnknownNoTrue if the rider does not have the airport pickup flight information.
user_confirmedYesTrue only after the user approved the trip, price and amount due if quoted, contact information, and booking contact disclosure.
idempotency_keyYesGenerate one random value of 16 to 64 characters per booking. Reuse that exact value on any retry the tool permits. Use a new value for a separate booking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already disclose readOnlyHint=false, openWorldHint=true and idempotentHint=true, yet the description adds real substance: payment link return, deposit saving the card for an automatic balance charge, and availability risk that payment does not guarantee the ride. It stops short of describing failure modes or what happens if the quoted fare changed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short sentences, front-loaded with the action and its return value, then edge cases (Sprinter requests) and finally the field-copying rule. Dense but every sentence carries information; 'request_estimate trips' is mild jargon drawn from elsewhere.

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 35-parameter, nested-object mutation with no output schema, the description covers the essential mechanics: confirmation requirement, payment link output, deposit vs full fare, and which fields come from the quote. What the hosted link response otherwise contains and post-submission failure handling are left unstated.

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 description coverage is 100%, so a 3 is the floor; the description earns more by giving cross-tool semantics the schema cannot express — fare_cents, stage and due_now_cents must be passed verbatim as get_quote returned them, and trip fields must match the quoted request. That directly guides how 35 parameters should be filled.

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 ('Submit a trip the user confirmed') and immediately names the deliverable ('Return a hosted payment link'). It also implicitly separates this tool from its sibling get_quote by requiring the very fields get_quote returned.

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 clear preconditions (user confirmed the trip; fields copied from get_quote) and flags the Sprinter hourly/one-way exception where the submit is only a request. It does not explicitly say when to call get_quote or get_service_info instead, so an agent must infer the quote-first flow.

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