Skip to main content
Glama
Sign In
mcp-document-intelligence

mcp-document-intelligence

by AndreasDietzel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

batch_organize

Rename and move multiple files in bulk from a defined operation list, with move/copy modes, backup for undo, and detailed reporting.

Instructions

Batch rename and move files according to a list of operations. Supports move/copy mode, automatic backup for undo, and detailed reporting.

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": {
      "baseFolder": "<baseFolder>",
      "operations": "<operations>"
    },
    "name": "batch_organize"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoOperation mode (default: move)
baseFolderYesBase folder for target structure
operationsYesArray of {originalPath, targetFolder, newFilename}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.6.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden; it usefully discloses the move-vs-copy mode, that an automatic backup is created to enable undo, and that the result includes detailed reporting. It omits critical behavior for a destructive file operation: permission requirements, conflict handling when a target already exists, and whether partial failures leave the file set half-reorganized.

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?

Two tight sentences with the primary action front-loaded and the supporting capabilities (mode, backup, reporting) following. Nothing is wasted, though the trailing feature list could have been traded for conflict/error semantics.

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 batch mutation tool with no annotations and no output schema, the description covers the recovery story (backup for undo) and reporting but leaves the riskiest aspects undefined: what happens on name collisions, whether the batch is atomic, and what the report contains. Adequate but with clear gaps for a file-moving operation.

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?

Schema description coverage is 100%, so the enum for mode and the baseFolder/operations definitions are already documented in the schema. The description restates move/copy mode and the operations list without adding format, path-resolution, or ordering semantics beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb pair and resource ('batch rename and move files') plus the driving input ('a list of operations'), so the core action is unambiguous. It does not, however, differentiate itself from siblings like auto_organize, smart_rename, or the single-item rename_document/move_document, leaving the agent to infer the boundary.

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?

Usage is only implied: 'according to a list of operations' signals this is for explicit, caller-specified batches rather than inferred organization. There is no explicit when-to-use/when-not or named alternative, and the reference to 'backup for undo' hints at undo_operation without stating the relationship.

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

Deploy Server

Other Tools