Skip to main content
Glama

apply_plan

Applies an approved cleanup plan by moving files into organized folders without deleting anything, so users can safely execute previewed rename and sort actions.

Instructions

Apply a plan the user has approved. Files are moved, never deleted.

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": {
      "plan_id": "<plan_id>"
    },
    "name": "apply_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes

Output Schema

NameRequiredDescriptionDefault
movesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • removedOutput schema / $defs / Move / properties / destination / format
      Removed value: -"path"
    • removedOutput schema / $defs / Move / properties / source / format
      Removed value: -"path"
  2. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare that the operation is not read-only and not destructive; the description adds useful behavioral context by clarifying that files are moved rather than deleted. It could go further on reversibility or idempotency, but the core safety-relevant behavior is disclosed.

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 two short, front-loaded sentences with no wasted wording. It communicates purpose and safety behavior efficiently.

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

Completeness3/5

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

The output schema and annotations cover return values and safety profile, and the description explains the approved-plan precondition. However, for a tool whose sole parameter is undocumented, it should ideally point agents to how plan_id is produced or selected.

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?

The schema has 0% description coverage and the only parameter, plan_id, is not explained in the description. The phrase 'a plan the user has approved' implies the ID refers to an approved plan, but it provides no source, format, or retrieval guidance for the parameter.

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 gives a specific verb and resource: apply an approved plan. It is clear what the tool does, though it does not explicitly name sibling tools such as plan_tidy or undo to differentiate itself.

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 states the key precondition that the plan must already be approved by the user, which is useful usage context. It does not explicitly say when to prefer undo or how plan_id should be obtained, so it stops short of full alternative guidance.

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