Skip to main content
Glama

Miami Black SUV

Get a fare and payment quote

get_quote
Read-onlyIdempotent

Quote a trip using the website fare. The hot field is an internal availability flag. fare_cents is the price the user pays. Provide flight details or acknowledge when they are unknown for an airport pickup. Some trips are request-only. Fares are subject to availability. For a typed address, the passenger enters the address on the site. For a Sprinter hourly trip, the passenger selects the duration on the site.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_quote"
  }
}

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.
legsNoPickup dates and times in the cruise package's leg order.
timeNoPickup time in Miami, HH:MM in 24-hour time. For packages use legs.
hoursNoChoose a whole number of hours from 2 to 12 for Suburban hourly and 3 to 12 for Sprinter hourly.
flightNoArrival flight number for an airport pickup.
toTextNoDrop-off address when to is other, or stops for hourly Sprinter.
escaladeNoRequest the Cadillac Escalade upgrade where offered, subject to availability.
fromTextNoPickup address when from is other.
hotelTextNoHotel name or address for a cruise package with a hotel stop.
packageIdNoCruise package ID from get_service_info.
childSeatsNoPaid child seats by type.
passengersNoPassenger count, including children. Defaults to one.
returnTripNoReturn leg for a point-to-point round trip.
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.
flightUnknownNoTrue if the rider does not have the airport pickup flight information.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely new behavior: fares are subject to availability, some trips return as request-only rather than a firm price, and fare_cents is what the rider actually pays. It does not explain pagination or failure responses, but for a read-only quote tool this is solid added context.

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

Conciseness3/5

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

Sentences are short but read as scattered notes rather than a structured narrative; several, like the remark about the internal 'hot' flag (a field not present in the input schema), are cryptic without context. The core purpose is stated first, which is good, but the ordering after that does not prioritize what an agent needs to decide and populate a call.

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

Completeness2/5

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

This is a 20-parameter tool with nested objects (returnTrip, legs, childSeats), two enums, and zero required parameters, so the description carries a heavy burden it does not meet. It never explains which parameters belong to which serviceType, when legs replaces date/time, or how sprinterMode and hours combine, leaving the agent to infer call shape from the schema alone.

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 100%, so every parameter is already documented in the schema, and the baseline is 3. The description adds only marginal parameter meaning, clarifying that the rider enters the typed address on the site for 'other' locations and selects the Sprinter hourly duration themselves, but it never explains how serviceType, packageId, or legs interact across the 20 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource: quote a trip against the website fare. It is clear this is a pricing/availability lookup rather than a booking, but it never names create_booking or get_service_info as the adjacent steps, so the agent must infer the sibling boundary from titles alone.

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?

There is conditional guidance embedded in the text: supply flight details or set flightUnknown for airport pickups, and some trips are request-only. However, it never states when to call this versus create_booking, nor which serviceType combinations are valid, so the guidance is implied rather than explicit.

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