Skip to main content
Glama

batch_rename

Rename files in bulk by regex find/replace, case, template, or extension, filtered by glob. Preview changes before applying, with collision checks and undo.

Instructions

Rename files in a folder: find/replace (regex), case, template ({name} {n} {ext}), extension; match glob. Preview unless apply; collision-checked; undo id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "batch_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
padNo
caseNo
findNo
pathNo
undoNo
applyNo
matchNo
startNo
replaceNo
templateNo
extensionNo
ignore_caseNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the single destructiveHint=false annotation, the description discloses that the operation is dry-run by default, that names are collision-checked, and that an undo id is issued — precisely the facts that justify treating a bulk rename as safe. It stops short of explaining what the preview returns or what happens to files that fail collision checks.

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

Conciseness4/5

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

Dense, front-loaded and free of filler — capabilities first, then the safety/mode clauses. The telegraphic semicolon fragments are efficient but occasionally force the reader to infer relationships between clauses.

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?

For a 12-parameter mutation tool with no output schema and near-zero annotation coverage, the description covers the core operation and its safety model but leaves four parameters and the template/glob syntax details unexplained. Adequate to start, not complete enough to call confidently on the first try.

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?

With 0% schema coverage the description must carry all parameter meaning, and it does define find/replace, case, template placeholders ({name} {n} {ext}), extension, match, apply and undo. However pad, start, path and ignore_case are never mentioned or exemplified, leaving a third of the 12 parameters opaque.

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?

Opens with a specific verb+resource ("Rename files in a folder") and enumerates the supported rename modes (find/replace regex, case, template, extension, glob match), so an agent knows exactly what the tool can transform. It does not name or route away from any sibling tool, which keeps it short of a 5.

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?

"Preview unless apply" gives a clear default-mode rule and the mention of an "undo id" hints at reversibility, so usage is implied at the level of a dry-run-then-apply workflow. There is no explicit guidance on when this tool is preferable to a plain regex or find_duplicates call, and no stated prerequisites for the folder.

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