Skip to main content
Glama

submit_plan

Submit a full revised plan or review/sign off the current version as-is, collecting independent reviews or final sign-offs and returning the final markdown document.

Instructions

Submit a full next plan version, or omit plan to review or sign off the latest version as-is without creating a version. This also recovers a stopped planner run with phase: "plan". If no version exists yet, pass plan. You write revised plans from agent input/reviews; tag contributing agents on steps and explain which amendments you accepted or rejected and why. Default final: false collects independent reviews and leaves the session awaiting_revision. Set final: true to collect sign-offs, close, and return the final markdown document; with a supplied plan this is allowed straight after input without a review. Show that final document to the user verbatim, including input and sign-offs. A failed phase leaves the previous state intact so you can retry.

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": {
      "ultraplan_id": "<ultraplan_id>"
    },
    "name": "submit_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoOptional: omit to have the latest version reviewed as-is (final false) or signed off as-is (final true), without creating a version. Pass the full next version, not a patch. If no version exists yet: No plan version exists yet; pass plan.
finalNoDefault false: review and leave open. True: collect sign-offs and finalize.
ultraplan_idYesThe ultraplanId from start_ultraplan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world mutation, so the bar is lower, yet the description adds real context: a failed phase leaves the previous state intact so retries are safe, and final:true returns the final markdown document that must be shown verbatim including input and sign-offs. It does not touch on idempotency or open-world effects, but the state-transition and retry semantics are genuinely useful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with the core purpose, and most sentences carry load-bearing behavioral rules (tag contributing agents, show the final document verbatim). However it is a single dense paragraph mixing purpose, workflow instructions, and edge cases, with no structure, making it harder to parse than it needs to be.

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

Completeness4/5

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

For a 3-parameter mutation tool with no output schema, the description covers session state outcomes, retry safety, and what the returned final document contains, which is enough for an agent to call it correctly. The only residual gap is the unclear reference to a 'phase' that does not appear in the schema.

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 100%, so the baseline is 3, and most of the description's parameter explanation ('full next version, not a patch', omit-to-review, final:false vs true) restates what the schema already documents. The one added detail, recovery via phase 'plan', refers to something not present in the schema and is ambiguous as written.

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 opens with a specific verb and resource ('Submit a full next plan version') and immediately clarifies the second mode (omit plan to review/sign off the latest version without creating a version). An agent can distinguish the two operating modes without opening the schema, though it never contrasts itself with sibling tools like submit_work or amend_contract.

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?

Rich conditional guidance: default final:false collects independent reviews and leaves the session awaiting_revision, final:true collects sign-offs and closes, and a supplied plan may be finalized straight after input without a review. It also states it recovers a stopped planner run, giving a clear trigger. What's missing is any explicit steering away from similar siblings.

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