Skip to main content
Glama

plan_tidy

Builds a dry-run plan to rename and sort files in a folder without moving anything, letting users review the proposed organization before applying changes.

Instructions

Build a dry-run plan for a folder. Nothing is moved. Show the plan to the user.

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": {
      "path": "<path>"
    },
    "name": "plan_tidy"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo

Output Schema

NameRequiredDescriptionDefault
idYes
rootYes
movesNo
createdYes
extra_rootsNoFolders outside root that config rules may move files into

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 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"
    • removedOutput schema / properties / extra_roots / items / format
      Removed value: -"path"
    • removedOutput schema / properties / root / format
      Removed value: -"path"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and openWorldHint=false; the description adds the useful guarantee "Nothing is moved", which is the key safety fact for a planning tool. However, readOnlyHint=false suggests the call does persist something (presumably a plan artifact), and the description never says so or where the plan lives.

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 action and immediately followed by the safety guarantee. Nothing is padded and nothing is buried.

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?

An output schema exists, so return values needn't be described, and the dry-run guarantee is stated clearly. The gaps are the undocumented limit parameter and the unexplained non-read-only side effect implied by readOnlyHint=false.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it doesn't. "A folder" loosely implies the path parameter, but the limit parameter (default 500) is left entirely unexplained — 500 files, 500 results, or a recursion depth cap?

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?

"Build a dry-run plan for a folder" names a concrete verb (build a plan) and resource (folder), and the phrase "dry-run" implicitly sets it apart from apply_plan in the sibling list. It stops short of naming apply_plan or scan_folder explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines3/5

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

"Show the plan to the user" hints at the workflow position (plan first, review, then presumably apply_plan), but the description never names apply_plan as the follow-up or says when to prefer scan_folder instead. Usage is implied rather than spelled out.

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