Skip to main content
Glama

Seatac Co trip planner

Get the booking link

get_checkout_link
Read-onlyIdempotent

When the traveler is ready to book: returns checkout_url, the one link to send them. It opens "Book your trip" on seatac.co, which lists every part to book, in any order, each paid on its own: the trip itself (the cruise or event tickets, with a partner), the flight (with a partner), the hotel (on seatac.co's room page), and the rides (by licensed partner operators, paid together in one card payment on seatac.co), timed to the flight, hotel and sailing. A ride waits only for what it connects to: to or from Seatac for its flight, to or from the hotel for the hotel, to or from the pier for the sailing (booked, booked elsewhere or not needed all unlock it); a waiting ride says so in waits_for. booking_order lists each part, its items and a suggested next. This tool books and charges nothing; the traveler confirms and pays on seatac.co.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "get_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesplan_id from plan_trip.

Output Schema

NameRequiredDescriptionDefault
plan_idYes
checkout_urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations, the description explains that the link opens a booking page on seatac.co, lists each component to book and pay separately, describes ride-waiting logic and waits_for, and notes that booking_order lists parts and suggested next steps. It also confirms the tool books and charges nothing, which is consistent with the readOnlyHint annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the key action and return value, but it is a dense single paragraph with long nested clauses about parts, payment, and ride waiting. Much of this detail is useful context, yet the structure could be tighter and easier to scan.

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?

Given the presence of an output schema, the description need not document return values exhaustively, but it still explains the meaning of checkout_url, waits_for, and booking_order. Combined with annotations covering safety and idempotency, it is complete enough for an agent to call the tool correctly.

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?

There is only one parameter, plan_id, and schema coverage is 100%; the schema already describes it as coming from plan_trip. The description does not add any further meaning about plan_id, so the baseline of 3 is appropriate.

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 states a specific action and output: it returns checkout_url, the single link to send the traveler. It clearly establishes that this is a link-retrieval tool and not a booking tool, though it does not explicitly name or contrast with the sibling 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?

It gives a clear usage condition: use it when the traveler is ready to book. It does not provide explicit when-not guidance or name alternative tools, but the context is sufficient to select it.

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