Skip to main content
Glama

Seatac Co trip planner

Quote a Seatac Co ride

quote_ride
Read-onlyIdempotent

Get the live fare for a specific Seatac Co ride, per eligible vehicle, priced exactly as seatac.co checkout prices it. Each vehicle includes a booking_url where the customer reviews and pays. Rate limited; reuse a quote instead of re-requesting it.

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": {
      "pickup": "<pickup>",
      "pickup_datetime": "<pickup_datetime>",
      "passengers": "<passengers>"
    },
    "name": "quote_ride"
  }
}

Input Schema

NameRequiredDescriptionDefault
bagsNoNumber of checked-size bags (0-12).
hoursNoSet only for an hourly charter: the number of hours (1-24).
pickupYesPickup location. Street address, hotel, or place in the Seattle area, e.g. "Seattle-Tacoma International Airport", "Pier 91", "Hyatt Regency Bellevue", or "1301 5th Ave, Seattle".
dropoffNoDrop-off location. Street address, hotel, or place in the Seattle area, e.g. "Seattle-Tacoma International Airport", "Pier 91", "Hyatt Regency Bellevue", or "1301 5th Ave, Seattle". Optional for hourly charters.
passengersYesNumber of passengers (1-12).
flight_numberNoOptional flight number for Seatac pickups or drop-offs, e.g. AS 123.
pickup_datetimeYesPickup date and time, ISO 8601. Without an offset it is read as Seattle local time (America/Los_Angeles), e.g. 2026-11-02T14:30.

Output Schema

NameRequiredDescriptionDefault
tripNo
errorNo
vehiclesNo
booking_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "booking_url": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "trip": {
      +      "type": "object"
      +    },
      +    "vehicles": {
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive behavior. The description adds material context beyond that: live fare behavior, per-vehicle eligibility, exact checkout pricing, a booking_url for review/payment, and rate-limit reuse guidance.

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?

The definition is three tightly written sentences, front-loads what the tool returns, and includes only operationally relevant details such as the booking_url and rate-limit reuse guidance. There is no filler.

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?

An output schema exists, so the description needn't explain return values, and the schema fully covers parameters. The description still adds useful context about pricing fidelity, booking flows, and rate limits, though it leaves some ambiguity around what 'eligible vehicle' means.

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 the schema already documents all seven parameters in detail. The description does not add parameter-specific meaning beyond referring generally to a ride and eligible vehicles, which is appropriate but not enriching.

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 description uses a specific verb ('Get the live fare') and resource ('Seatac Co ride') and clarifies that pricing is per eligible vehicle and matches checkout. It does not explicitly distinguish this tool from sibling comparison tools such as compare_parking_vs_ride, so it falls short of a 5.

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?

It gives a useful reuse instruction tied to rate limiting ('reuse a quote instead of re-requesting it'), but it does not say when to choose this over compare_* or start_booking/get_checkout_link. The usage context is implied rather than explicitly routed.

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