Skip to main content
Glama

Get a fare quote

get_quote
Read-onlyIdempotent

Get a transparent, all-in fare quote for a Quo black-car ride in Florida. No account needed, the same price shown on the public site. Returns a line-item breakdown and the total. Pass pickup and dropoff to have the trip routed and priced by distance exactly as a reservation is; without them the total is an estimate before routing, and a longer trip costs more when it is reserved.

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": {
      "vehicle": "<vehicle>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHours booked, for service=hourly (minimum 2); defaults to 3 if omitted. Ignored for service=transfer.
pickupNoPickup address, airport, or hotel. With dropoff (or for hourly, alone), the trip is routed and the quote includes distance, as a reservation's would.
dropoffNoDestination, for service=transfer.
serviceNotransfer = point-to-point; hourly = by the hour, as directedtransfer
vehicleYesVehicle class: sedan (Executive Sedan), suv (Luxury SUV), sprinter (Executive Sprinter), flagship (Flagship)
eventSlugNoSlug of an event on the Quo calendar (see list_events) if this ride is tied to one, affects demand pricing

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.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, closed-world), and the description adds genuinely new behavioral facts: the price matches the public site, no account or auth is required, the response contains a line-item breakdown plus total, and routing materially changes the number. It stops short of saying whether a quote is guaranteed or how long it stays valid, which matters for a pricing tool.

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?

Three sentences, front-loaded with the core promise, then the auth and return-value facts, then the routing caveat. Every sentence carries information, though the final clause ('a longer trip costs more when it is reserved') is slightly convoluted for the point it makes.

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?

With no output schema, the description steps in to say what comes back (line-item breakdown and total), and the six parameters are fully documented in the schema while the description supplies the routing/pricing relationship between them. Nothing an agent needs in order to call this correctly and interpret the result is missing.

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 the baseline is 3, but the description adds the interaction the schema only states piecemeal: pickup+dropoff (or pickup alone for hourly) triggers routing and a distance-based price, and omitting them yields an estimate that will understate a longer reserved trip. That relational caveat is meaning beyond the field-level text.

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 names a specific verb and resource — a transparent, all-in fare quote for a Quo black-car ride in Florida — plus the scope (Florida, black-car) and the output shape (line-item breakdown and total). An agent can distinguish this from get_fleet, get_city_guide, and the reservation tools without opening any schema.

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 clearly frames the two modes of use: pass pickup and dropoff for a routed, reservation-grade price, or omit them for a pre-routing estimate, and it notes no account is needed. It never explicitly names reserve_ride or reserve_and_pay as the follow-on action, so the boundary with the booking siblings is implied rather than stated.

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