Skip to main content
Glama

Seatac Co trip planner

Check a trip plan

check_plan
Read-onlyIdempotent

Check a plan before booking: timing problems (a flight home too early for the ship, a stop that makes them late), what's still missing (hotel, flight times), rides that can't be booked yet, the cost so far line by line, hotel options, and booking_order: every part to book (the trip, the flight, the hotel, the rides; any order, a suggested next), what's done, and which rides still wait for the flight, hotel or sailing they connect to. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
plan_idYesplan_id from plan_trip.

Output Schema

NameRequiredDescriptionDefault
okYes
plan_idYes
plan_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, and the description's 'Read-only' adds little there. The valuable extra is the behavioral scope of the check: timing conflicts, missing reservations, unbookable rides, line-by-line cost, and dependency-aware booking order. It does not discuss rate limits or side effects, but for a read-only validator that is acceptable.

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 lead clause is front-loaded and useful, but the remainder is a single run-on sentence with parenthetical asides and an awkward mid-sentence 'booking_order:' list. The content is dense and relevant, but its structure makes it harder to scan than necessary.

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 read-only validation tool with a complete one-parameter schema, full annotations, and an output schema, the description supplies enough context to call it correctly: when to use it and what kinds of findings it returns. It could be improved by pointing to get_plan or start_booking alternatives, but nothing essential is missing.

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?

The only parameter, plan_id, is fully described in the schema as coming from plan_trip; the description neither repeats nor enriches that. With 100% schema coverage, the schema does the work and the description appropriately stays out of parameter details.

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 opens with a specific verb and resource, 'Check a plan before booking,' and enumerates the checks it performs: timing problems, missing items, costs, hotel options, and booking order. The purpose is unmistakable, but it does not explicitly contrast itself with siblings such as get_plan 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?

It states the key usage context, running this before booking, and implies it validates an existing plan rather than creating or retrieving one. However, it does not name alternatives or exclusions, such as using get_plan for a plain retrieval, so the guidance is clear but incomplete.

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