Skip to main content
Glama

Seatac Co trip planner

Take something off the plan

remove_from_plan
DestructiveIdempotent

Take one thing off a plan by its item_id (from add_to_plan or get_plan), or "hotel", "flight" or "cruise". Returns the updated summary and plan_url.

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_id": "<item_id>"
    },
    "name": "remove_from_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYesitem_id, or hotel, flight or cruise.
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.
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
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true and non-read-only, so the safety profile is covered. The description adds the return payload (updated summary and plan_url) and the ability to remove by category, but says nothing about irreversibility, missing-item behavior, or edit_key authorization beyond the 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?

Two tight sentences, essential behavior first with the return values trailing. No filler, though the category parenthetical is slightly awkwardly spliced into the first sentence.

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?

An output schema exists, so return values need no exposition, and the destructive/idempotent annotations carry the safety story; the description supplies the id provenance and shortcut values needed to call it correctly. Only the failure and reversibility behavior is left implicit.

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 100%, so plan_id, edit_key and item_id semantics are already documented. The description only repeats the id provenance and the hotel/flight/cruise shortcut already present in the schema, adding little beyond baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (remove) and resource (one item on a plan), and the parenthetical naming add_to_plan/get_plan as the id sources plus the category shortcuts makes it unmistakably the inverse of add_to_plan.

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?

Tells the agent where the identifiers come from (add_to_plan or get_plan), which is the key prerequisite for calling it, but never states when not to use it or what happens if the item is not on the plan.

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