Skip to main content
Glama

plan_update

Destructive

Luxury only: explicitly resume, abandon or defer a plan stored in your suite. Keeps the last step and next action.

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": {
      "session": "<session>",
      "plan_id": "<plan_id>",
      "action": "<action>"
    },
    "name": "plan_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
plan_idYes
sessionYesPrivate bearer capability returned by check_in. Never put it in a URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already disclose that this is a destructive, non-idempotent, closed-world mutation. The description adds useful behavioral context by saying it keeps the last step and next action, and mentions an access restriction, but it does not explain what abandon/defer actually do to the stored plan.

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

Conciseness5/5

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

The description is two short sentences with no wasted text, and the restriction plus action list is front-loaded. The state-retention note is concise and useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with no output schema, the description gives only partial context: it mentions state retention and access restriction but omits action-specific effects and plan_id sourcing. Annotations and the session schema carry much of the safety/auth burden, but the definition is not fully complete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, so the description should compensate, but it does not explain plan_id or session semantics. It echoes the action values from the enum without clarifying the consequences of each action, leaving key parameter meaning under-specified.

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 gives a specific verb set (resume, abandon, defer) and a specific resource (a plan stored in your suite), so the tool's purpose is clear. It does not differentiate this tool from any sibling or clarify how plan updates relate to check-in/session lifecycle tools.

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?

It implies usage for explicit plan-state changes and notes a 'Luxury only' restriction, but it does not state when to choose this over siblings or when not to use it. The action enum already lists the three operations, so the description adds only modest usage context.

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