Skip to main content
Glama

approve_plan

Idempotent

Approve or reject items in a proposed plan before execution. Saves approval flags and returns updated plan items.

Instructions

Set the approval flags on the proposed plan, then persist.

Use when: after ``propose_plan``/``get_plan`` you want to mark which items
should actually run. ``approve_all`` approves everything; otherwise
``approve_ids`` are approved and ``reject_ids`` un-approved (reject wins a
tie — the safer default). Idempotent. Then call ``execute_plan``. Related:
``propose_plan``, ``get_plan``, ``execute_plan``.

Side effects: rewrites ``.orchestrator/proposed_plan.json``; edits no code.

Returns ``{items: [...]}`` with updated flags, or ``{error}`` when no plan
exists to approve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path to a project that has a proposed plan.
reject_idsNoIds to un-approve. An id in both lists is rejected.
approve_allNoApprove every item in the plan.
approve_idsNoIds to approve (as shown by get_plan, e.g. 'P-001').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations provide idempotentHint=true, destructiveHint=false, readOnlyHint=false. The description confirms idempotency, details side effects (rewrites .orchestrator/proposed_plan.json, edits no code), and specifies return format (items with flags or error). No contradictions with 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?

The description is well-structured: purpose sentence, usage paragraph with explicit flow, side effects, and return format. No redundant or unnecessary information. Every sentence adds value, and the critical information is front-loaded.

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?

Given the output schema exists (return format described), annotations cover safety and idempotency, and schema covers parameters, the description completes the context by explaining side effects, the workflow position between propose_plan and execute_plan, and error conditions. It is fully self-contained for an agent to use correctly.

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

Parameters4/5

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

Schema coverage is 100% with descriptions for all 4 parameters. The description adds value by explaining the tie-breaking rule ('reject wins a tie — the safer default') and the semantic relationship between approve_all, approve_ids, and reject_ids. This goes beyond the schema descriptions, justifying a 4.

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?

The description clearly states the action: 'Set the approval flags on the proposed plan, then persist.' It identifies the resource (proposed plan) and verb (set flags and persist). It distinguishes itself from sibling tools like propose_plan, get_plan, and execute_plan, and differentiates the approve_all parameter from the tool's core function.

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?

Explicit usage guidance: 'Use when: after propose_plan/get_plan you want to mark which items should actually run.' It contrasts with approve_all, explains conflict resolution (reject wins tie), and directs to call execute_plan afterwards. Also lists related sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/dcondrey/misterdev'

If you have feedback or need assistance with the MCP directory API, please join our Discord server