Skip to main content
Glama

Seatac Co trip planner

Add to the trip plan

add_to_plan
DestructiveIdempotent

Add one thing to a plan: hotel, flight details, cruise, tour or experience, restaurant, event, meeting, parking or rental_car (rides are planned automatically). A hotel, flight or cruise replaces the one already in the plan. Adding the same thing again changes nothing. Returns item_id (for remove_from_plan), the updated summary and the same plan_url, which now shows it.

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>",
      "edit_key": "<edit_key>",
      "item": "<item>"
    },
    "name": "add_to_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
plan_idYesplan_id from plan_trip.
edit_keyYesedit_key from plan_trip. Keep it private: it lets you change the plan.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

The description earns its keep beyond the annotations by specifying exactly what gets destroyed (a hotel, flight or cruise replaces the existing one) and confirming idempotency ("Adding the same thing again changes nothing"), which directly substantiates destructiveHint and idempotentHint. It also names the return payload and explains that plan_url is stable and now reflects the new item, which is behavior the annotations cannot convey.

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?

Four tight sentences, front-loaded with the item-type enumeration, with no filler. The replacement and idempotency rules are packed efficiently, though the type list and the return-value sentence could be slightly trimmed given the output schema already documents the return shape.

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 mutation tool with a nested 15-field item object and an output schema, the description covers the critical ambiguities: replacement semantics, idempotency, ride exclusion, and the item_id handoff. The remaining gap is procedural context (that plan_id and edit_key come from plan_trip, and that edit_key is sensitive), which is only present in the schema.

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 coverage is 67% and the nested item object is well documented per-field, so the baseline applies. The description adds only marginal meaning beyond the schema: the ride-type exclusion and the item_id-to-remove_from_plan linkage; it says nothing about plan_id/edit_key handling or which item fields are mandatory per type.

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 ("Add one thing to a plan") and enumerates the accepted item types, so the agent knows exactly what goes in. It partially differentiates from siblings by noting item_id feeds remove_from_plan and that rides are handled automatically, but it does not distinguish itself from plan_trip or the itinerary-specific planners.

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?

Usage is implied rather than stated: "rides are planned automatically" quietly tells the agent not to add rides, and the item_id reference implies remove_from_plan is the counterpart. There is no explicit when-to-use framing, no prerequisite stating a plan must exist first (plan_id/edit_key provenance lives only in the schema), and no naming of alternative tools.

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