Skip to main content
Glama

terminal_plan

Read-onlyIdempotent

Preview and validate a supported development command without running it, so you can inspect the planned action before execution.

Instructions

Plan a supported development command without executing 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": {
      "project_path": "<project_path>",
      "action": "<action>"
    },
    "name": "terminal_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
scriptNo
project_pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description is consistent with them by emphasizing non-execution. However, it adds nothing about what a "plan" returns (resolved command string, validation result, warnings), whether it can fail, or what "supported" commands are rejected.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the terseness is partly the cause of the parameter and return-value gaps.

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

Completeness2/5

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

For a tool with an undocumented 9-value enum, an unexplained optional script parameter, and no output schema, the description should say what a plan produces and how action/script interact. None of that is covered, leaving the agent to guess at invocation details.

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 0%, so all three parameters are opaque: the description never explains project_path, the nine-value action enum, or when the optional script parameter is required (evidently for powershell-script). With no schema documentation and no compensating text, an agent gets no semantic help here.

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 names a specific verb ("Plan") and resource ("a supported development command") and adds the key qualifier "without executing it," which lets an agent separate it from an executor such as terminal_run. It stops short of naming the execution sibling outright, so the distinction 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 Guidelines3/5

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

The phrase "without executing it" implies a preview/dry-run use case, but there is no explicit when-to-use or when-not-to-use guidance and no named alternative for actually running the command. The agent must infer that planning precedes execution.

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