Seatac Connection rides

Search flights to or from Seattle

search_flights

Read-onlyIdempotent

Live airfares for a trip to or from Seattle (SEA), cheapest first, priced exactly as seatac.co prices them (taxes and fees included, USD). Each result lists the flights, times, stops, fare terms and bags; booking_url opens seatac.co's flight search on the same trip, where the traveler picks the flight and pays. One of origin or destination must be SEA. Rate limited; reuse results instead of re-searching.

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": {
      "origin": "<origin>",
      "destination": "<destination>",
      "depart_date": "<depart_date>"
    },
    "name": "search_flights"
  }
}

Input Schema

Name	Required	Description
`adults`	No	Travelers 12 and older (1-9, default 1).
`origin`	Yes	3-letter airport code, e.g. SEA or JFK.
`infants`	No	Under 2, on a lap (default 0).
`children`	No	Ages 2-11 (default 0).
`depart_date`	Yes	YYYY-MM-DD.
`destination`	Yes	3-letter airport code, e.g. LAX or SEA.
`return_date`	No	YYYY-MM-DD for a round trip; omit for one way.
`nonstop_only`	No	Only nonstop flights (default false).

Output Schema

Name	Required	Description	Default
`note`	No
`trip`	No
`error`	No
`found`	No
`flights`	No
`booking_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent and openWorld, and the description adds substantial context beyond that: exact pricing semantics (taxes and fees included, USD), ordering (cheapest first), what each result contains, that booking happens off-tool via booking_url, and an explicit rate limit. This is exactly the value-add behavior disclosure expected when annotations cover only the safety profile.

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?

Four compact sentences, front-loaded with the resource and scope, then results, then the booking handoff, then the operational constraint. No filler or restatement of the name/title.

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 an output schema available, the description needn't enumerate return fields, yet it still summarizes result contents and the booking_url affordance. Combined with the SEA constraint and rate-limit warning, an agent has everything needed to call it correctly and avoid redundant searches.

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 coverage is 100%, so the baseline is 3, but the description adds a genuine cross-parameter constraint not expressible in the schema: one of origin or destination must be SEA. That is real added meaning for invoking the tool correctly rather than repeating per-field docs.

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 ('Live airfares for a trip to or from Seattle') plus scope (SEA-anchored, cheapest first, taxes/fees included in USD). The Seattle-only constraint and fare-ordering make it immediately distinguishable from siblings like compare_airport_options or start_booking.

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 operating context: one of origin or destination must be SEA, results are rate limited so reuse them, and booking_url is the handoff point where the traveler actually pays. It does not explicitly name a sibling as an alternative for comparison-style tasks, so it stops short of full when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Seatac Connection rides tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?