Skip to main content
Glama

project_plan

Destructive

Exports deterministic plan.json for a specified project, marking status as planned and not applying changes to Proteus. Use it to generate a reviewable plan before edits.

Instructions

Export deterministic plan.json. Status is planned, not applied to Proteus.

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": "<project>"
    },
    "name": "project_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.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=false and destructiveHint=true; the description usefully adds that the export is deterministic and leaves the Proteus project itself unmodified. However, it never states where plan.json is written or whether an existing file is overwritten, which is exactly the risk the destructive annotation signals — that gap creates mild tension with the reassuring "not applied" phrasing.

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 terse, front-loaded sentences with no filler; the key output artifact and the non-applying behavior lead. It is arguably too compressed rather than padded, given how much is left unsaid.

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?

With no output schema, an undocumented sole parameter, and a destructive annotation, the definition should say what is produced and where it lands. Neither the output location nor the overwrite semantics are covered, so an agent cannot call this with full confidence.

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?

There is one required parameter, project, with 0% schema description coverage, so the description carries the full burden of explaining it. It says nothing about whether project is a name, a path, or a handle, nor what form a valid value takes.

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 pairs a concrete verb (Export) with a concrete artifact (deterministic plan.json), which is enough to tell it is a serialization step rather than a mutation of the project. It does not differentiate itself from nearby export siblings such as export_netlist or export_svg, so an agent must infer the distinction from the name alone.

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?

"Status is planned, not applied to Proteus" implies a dry-run/preview role and hints that native_apply is the committing counterpart, but that alternative is never named and no when-not condition is stated. Usage is therefore implied rather than instructed.

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