Skip to main content
Glama

Seatac Co trip planner

When to leave for SEA

plan_airport_departure
Read-onlyIdempotent

Work out when to leave for Seatac (SEA) for a departing flight, the seatac.co departure planner's rule: be at the terminal 2 hours before a domestic or 3 hours before an international departure (SEA's advice), minus Seatac's stored typical drive from the starting point. Returns the terminal-arrival target, the pickup time, a prefilled ride booking link, and how long before departure to leave from each place we have a drive time for.

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": {
      "departure_datetime": "<departure_datetime>"
    },
    "name": "plan_airport_departure"
  }
}

Input Schema

NameRequiredDescriptionDefault
fromNoStarting point with a stored drive time.
drive_minutesNoOptional drive time in minutes (5-240) when starting elsewhere; overrides the stored time.
internationalNotrue for an international flight (3-hour rule); default false (2 hours).
pickup_addressNoOptional exact pickup address, prefilled in the booking link.
departure_datetimeYesScheduled departure, ISO 8601; Seattle local time when no offset, e.g. 2026-11-02T08:15.

Output Schema

NameRequiredDescriptionDefault
errorNo
notesNo
page_urlNo
pickup_atNo
booking_urlNo
drive_minutesNo
be_at_terminal_byNo
leave_before_departureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the bar is lower, yet the description still adds substantive behavior: the fixed 2h/3h buffer heuristic, subtraction of a stored per-origin drive time, and the fact that outputs include the terminal-arrival target, pickup time and a prefilled booking link. It stops short of documenting edge behavior (past departures, offsets, what happens when no drive time exists for an origin), which keeps it off a 5.

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?

Front-loaded with the core purpose and then the rule and outputs in a logical order. It is a single dense run-on with nested parentheses ('the seatac.co departure planner's rule', '(SEA's advice)') that could be tightened, but nothing is genuinely wasteful.

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?

With an output schema present, the description does not need to enumerate return values, yet it summarizes them helpfully while fully covering the decision rule and the one required input. For a deterministic calculation tool over five flat parameters this is essentially complete, minus noted edge-case behavior.

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, and the description largely restates the schema's semantics ('stored typical drive', booking-link prefill). The useful addition is that the tool can resolve a drive time 'from each place we have a drive time for', hinting at the multi-origin behavior, but it adds little else beyond the structured fields.

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 ('work out when to leave') applied to a specific resource (a SEA departure), and spells out the underlying computation: terminal-arrival buffer (2h domestic / 3h international) minus a stored typical drive. This is unmistakably distinct from pricing siblings like quote_ride or compare_airport_options.

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?

The context of use is clear ('for a departing flight') and the rule that governs the answer is stated, so an agent knows what the tool is for. However, there is no explicit when-not guidance and no named alternative (e.g. quote_ride for actual pricing, compare_airport_options for mode choice), leaving the routing decision to inference.

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