Skip to main content
Glama

show_plan

Displays every planned cut with its spoken content and the kept segments so you can review edits before applying them.

Instructions

Show every cut in a plan with what was said in it, plus the kept segments, for review before applying.

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": {
      "planId": "<planId>"
    },
    "name": "show_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. 'Show' signals a read-only inspection, and the description discloses the content of the response (cuts, transcript, kept segments), but it says nothing about whether transcript text is truncated, how large plans are handled, or any output limits.

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?

One front-loaded sentence with no filler; the read target and purpose come first. The phrase 'with what was said in it' is slightly loose but still economical.

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 single-parameter read tool with no output schema, the main gap is the undocumented planId source. The description adequately conveys what comes back, but leaves the agent guessing how to obtain the one required argument.

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?

The schema has 0% description coverage and the single parameter planId is undocumented in both schema and description. The description implies a 'plan' entity exists but never says how planId is obtained or what format it takes, so an agent cannot resolve the required argument from this text alone.

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?

A specific verb-plus-resource ('Show every cut in a plan') with the payload spelled out: each cut, its transcript ('what was said in it'), and the kept segments. It reads clearly against a mutating sibling implied by 'before applying', though no sibling is named outright.

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?

'For review before applying' gives a clear usage context: call this before committing cuts. It stops short of naming the apply step as an explicit alternative or stating when this tool should not be used.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.