Skip to main content
Glama

plan_fix

Generates a read-only plan to mechanically fix a dependency cycle, layer edge, or unused import. Use it when no behavior change is needed; nothing is written.

Instructions

Call only when the user asked for a mechanical fix of a cycle, a layer edge, or an unused import. Writes nothing. Skip for a behavior change. Pass confirm mechanical.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "plan_fix"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo
confirmNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool 'Writes nothing' and requires 'confirm mechanical,' but does not explain what the tool actually returns, whether it produces a plan, or any permissions or side effects.

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?

The text is short and front-loads the call condition. The final 'Pass confirm mechanical' is slightly telegraphic but still efficient and purposeful.

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 planning tool with no annotations, no output schema, and 0% parameter description coverage, the description is incomplete. It does not explain what the tool returns, how the plan is presented, or what the 'repo' parameter means.

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 the description must compensate. It clarifies that 'confirm' should be 'mechanical' but says nothing about the 'repo' parameter, leaving one of two parameters undocumented.

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

Purpose3/5

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

The description specifies trigger conditions (mechanical fix of a cycle, layer edge, or unused import) and notes 'Writes nothing,' but never explicitly states that the tool plans a fix. The purpose is inferable from the name and conditions, yet not stated as a clear verb+resource.

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?

It gives strong when-to-use guidance: call only for mechanical fixes and skip for behavior changes. It does not name an alternative tool, but the exclusion is explicit and precise.

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