Skip to main content
Glama

Propose plan

propose_plan
Read-only

Produce a structured execution plan for the user to review. Use this as your FINAL action in plan mode when you have concrete write operations to schedule. Each step names a real write tool and its parameters; steps execute in order after the user approves. Never call write tools directly in plan mode. If you have no writes to propose, end the turn with plain text instead of calling this tool.

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": {
      "title": "<title>",
      "summary": "<summary>",
      "steps": "<steps>"
    },
    "name": "propose_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYes
titleYesShort human-readable title for the plan.
summaryYesOne-paragraph overview of what the plan will do and why.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint=true annotation, it discloses the key behavioral model: the plan is reviewed and approved by the user before any step runs, steps run in order, and the tool itself performs no writes. It does not restate limits such as the 20-step cap or the skip-on-prerequisite-failure rule, which live in the schema, so it is not fully complete but adds real value over the annotations.

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?

Five short sentences, front-loaded with the core action and immediately followed by the timing constraint, the prohibition, and the fallback. Every sentence carries a distinct instruction with no redundancy.

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

Completeness5/5

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

For a nested-schema planning tool with a rich input schema and no output schema, the description supplies exactly what the schema cannot: when to emit the plan, that approval gates execution, and what to do when there is nothing to propose. Nothing needed to invoke it correctly is missing.

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

Parameters3/5

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

Schema coverage is 67% and the nested step schema already documents tool_name eligibility, depends_on_step_order, and length caps in detail. The description only reinforces that each step names a real write tool and its parameters, adding little beyond the structured fields.

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

Purpose5/5

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

States a specific verb and artifact ('Produce a structured execution plan for the user to review') and pins its role in the workflow ('FINAL action in plan mode'). An agent can distinguish it from write siblings and from other planning tools like ticket_draft_plan or plan_os_patches without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-to-use ('FINAL action in plan mode when you have concrete write operations to schedule'), an explicit prohibition ('Never call write tools directly in plan mode'), and an explicit when-not with the alternative ('If you have no writes to propose, end the turn with plain text instead'). No inference is required.

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.