Skip to main content
Glama

end_ultraplan

Destructive

Close an ultraplan without collecting sign-offs and return a markdown document marked not signed off, including the latest plan, agent input, and revision history to show the user verbatim.

Instructions

Close an ultraplan WITHOUT collecting sign-offs. Returns a markdown document marked not signed off with the latest plan, agent input and revision history (or no plan if none was submitted). Show the document to the user verbatim. Use submit_plan with final: true instead when you want sign-off.

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": "end_ultraplan"
  }
}

Input Schema

NameRequiredDescriptionDefault
ultraplan_idYesThe ultraplanId to close without sign-off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and non-idempotent, and the description does not contradict them — 'close without sign-off' is consistent with a destructive, non-idempotent termination. It adds real context beyond the annotations: the return is a markdown document marked not signed off containing the latest plan, agent input and revision history, with an explicit edge case for no plan submitted. It stops short of saying whether closing can be undone or whether an ultraplan can be re-opened, which keeps it at 4.

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?

Three short sentences, front-loaded with the distinguishing constraint, then the return value, then the alternative. Every sentence carries information an agent needs to select or invoke the tool correctly; there is no filler.

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?

With no output schema, the description carries the return-value burden and does so by naming the document type, its contents, and the empty case. Combined with annotations covering the safety profile and a fully documented single parameter, nothing material is missing for a one-parameter closing tool.

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?

There is a single parameter at 100% schema coverage, so the schema already explains ultraplan_id. The description's phrasing 'close without sign-off' reinforces the parameter's meaning but adds no format, sourcing, or validation detail beyond the schema; baseline 3 applies.

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 resource ('Close an ultraplan') and immediately narrows the scope with 'WITHOUT collecting sign-offs', which is exactly what separates it from the sign-off path. An agent can distinguish it from submit_plan and the other end_* siblings without opening a 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 an explicit when-to-use rule (closing without sign-off) and names the alternative, submit_plan with final: true, plus the condition that selects it. It also tells the agent what to do with the result ('Show the document to the user verbatim'), leaving nothing to inference.

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