Skip to main content
Glama

Seatac Co trip planner

Get the trip plan

get_plan
Read-onlyIdempotent

Read a plan: every day in order with its steps (flights, rides with pickup times and estimates, hotel, the cruise, things to do), what's booked, item_ids, the estimated total, summary_markdown to show in the chat, and plan_url, the visual plan page to share. 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": "get_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesplan_id from plan_trip.

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
plan_urlYesThe visual plan page for the traveler. Share this link.
summary_markdownNoA short day-by-day summary to show in the chat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the trailing 'Read-only' merely restates them. The description adds genuine value by going beyond annotations to describe payload shape (ordered days and steps, pickup times and estimates, booking status, plan_url), but it says nothing about behavior on a missing or stale plan_id, permissions, or response size.

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?

It is a single front-loaded sentence with the verb and resource first, followed by the payoff contents. The parenthetical inventory is dense but each item tells the agent something useful about the response; the redundant 'Read-only' tail is the only wasted phrase.

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 one required parameter, full schema coverage, complete annotations, and an output schema present, the description is sufficient to call the tool correctly and previews the response contents. The only shortfall is the absence of routing guidance among the many sibling plan tools.

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% for the single parameter, and the schema already states that plan_id comes from plan_trip, so the description adds no meaning beyond it. This is the expected baseline when the schema does the work.

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 ('Read a plan') and then enumerates the returned contents (days, steps, bookings, totals, summary_markdown, plan_url), so the agent knows exactly what it gets back. It does not name or contrast with related siblings such as check_plan or plan_trip, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no statement of when not to use it, and no named alternative such as check_plan for a lightweight status check or plan_trip for creating one. The only usage signal is the implied 'read a plan' and the schema note that plan_id comes from plan_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