Skip to main content
Glama

Seatac Co trip planner

Plan a SEA / Seattle trip

plan_trip

Creates a trip plan for a trip through Seattle-Tacoma Airport (SEA) or Seattle: rides, hotel, flights, a cruise from Seattle, tours and events in one plan, timed so it fits. Give the arrival date (or a cruise sailing), travelers, and anything already known; you can add the rest later with add_to_plan. Creates a stored plan and returns plan_id, edit_key (keep private; needed to change it), plan_url (the visual, shareable plan page: show this to the traveler), summary_markdown, what's still needed, warnings, and hotel_options. The rides between the airport, hotel, pier and stops are planned automatically. Nothing is booked or charged: the traveler books from plan_url.

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": "plan_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoThe day they leave (no cruise), YYYY-MM-DD. Or give nights.
kidsNoHow many of them are kids (default 0).
itemsNoMore to put on the plan right away (up to 12), each like add_to_plan's item, e.g. {"type":"tour","id":"space-needle","date":"2027-05-05"}.
startNoThe day they arrive in Seattle, YYYY-MM-DD. Optional with a cruise (default: the day before sailing).
nightsNoNights in Seattle instead of end (0-21, default 2). With a cruise the Seattle nights run to sailing day.
purposeNovacation (default), business, visit, event or other.
travelersNoEveryone traveling (1-14, default 2).
hotel_nameNohotel: or a hotel booked elsewhere, "name, address".
hotel_slugNoOne of our hotels (slug from hotel_options of an earlier answer, or recommend_hotels_with_rides).
cruise_shipNoA cruise from Seattle: the ship (from find_cruise_sailings).
home_airportNoflight: 3-letter code they fly from, e.g. ORD.
landing_timeNoflight: landing at SEA, Seattle time HH:MM.
return_flightNoflight: flight home, e.g. AS 38.
arrival_flightNoflight: arriving flight number, e.g. AS 23, only once booked (the plan then shows the flight in as booked). Before that give landing_time, or search_flights.
departure_timeNoflight: flight home's departure, Seattle time HH:MM.
cruise_sail_dateNoThe sailing date in Seattle, YYYY-MM-DD.
cruise_already_bookedNoThey already booked the cruise.

Output Schema

NameRequiredDescriptionDefault
nameNoThe plan's name, e.g. "Alaska cruise · May 7–14": use it when the traveler has more than one plan.
plan_idYes
edit_keyYes
plan_urlYesThe visual plan page for the traveler. Share this link.
summary_markdownNoA short day-by-day summary to show in the chat.
traveler_edit_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds real value by disclosing that a plan is persisted, that edit_key must be kept private, that inter-stop rides are auto-planned, and that no booking or charge occurs. That 'nothing is booked or charged' line is exactly the kind of nuance annotations cannot express. It omits idempotency behavior (repeat calls create a second stored plan), and much of the return-value list duplicates the existing output schema.

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?

The first sentence front-loads what the plan contains and the second states what to supply, so an agent can act after two sentences. The remainder is a compact run-down of returns and the no-charge guarantee. Some of that return enumeration is redundant with the output schema and could be trimmed.

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?

For a 17-parameter creation tool with annotations and an output schema, the description covers the essentials: minimum viable input, deferred completion via add_to_plan, persistence, privacy of edit_key, and absence of charges. The notable gap is sibling disambiguation against plan_seattle_trip and plan_cruise_trip, which an agent would have to resolve from schemas alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and every parameter carries inline meaning, including cross-references to sibling tools (pick_id from find_things_to_do, hotel slug from hotel_options, ship from find_cruise_sailings). The description adds only the high-level rule 'give the arrival date (or a cruise sailing), travelers, and anything already known,' which is a useful framing of which params matter first. With the schema this complete, that is sufficient.

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?

States a specific verb and resource ('Creates a trip plan') and enumerates the scope it covers: rides, hotel, flights, cruise, tours and events, timed so it fits. An agent understands the output is a stored, time-sequenced itinerary. It does not, however, differentiate itself from the sibling tools plan_seattle_trip and plan_cruise_trip, whose names suggest overlapping behavior.

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 concrete entry conditions (arrival date or cruise sailing plus travelers) and an explicit hand-off path: 'you can add the rest later with add_to_plan,' which routes the agent to the correct sibling for incremental edits. It also clarifies the boundary that nothing is booked here, the traveler books from plan_url. It stops short of saying when to choose this tool over plan_seattle_trip or plan_cruise_trip.

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