Skip to main content
Glama
AesirKode

enhanced-filesystem-mcp

by AesirKode

efs_batch

Batch file operations with atomic all-or-nothing execution, automatic rollback, and parallel support. Perform read, write, edit, delete, move, and list in one call.

Instructions

Execute multiple file operations atomically.

Features:

  • All operations succeed or all rollback

  • Automatic backups before modifications

  • Parallel execution when possible

  • Transaction support

All operations complete in a single call with automatic error handling.

Operations supported:

  • read: Read file

  • write: Create/modify file

  • edit: Find/replace in file

  • delete: Remove file

  • move: Move/rename file

  • list: List directory

Parameters:

  • operations: Array of operations to execute

  • atomic: Use transactions (all-or-nothing) (default: true)

  • parallel: Execute in parallel when safe (default: true)

Operation format: { op: 'read' | 'write' | 'edit' | 'delete' | 'move' | 'list', path: string, // op-specific fields... }

Examples:

  1. Read multiple files: { operations: [ { op: 'read', path: 'file1.txt' }, { op: 'read', path: 'file2.txt' }, { op: 'read', path: 'file3.txt' } ], parallel: true }

  2. Atomic refactoring: { operations: [ { op: 'edit', path: 'file1.js', oldText: 'oldName', newText: 'newName' }, { op: 'edit', path: 'file2.js', oldText: 'oldName', newText: 'newName' }, { op: 'move', source: 'old.js', destination: 'new.js' } ], atomic: true }

  3. Project setup: { operations: [ { op: 'write', path: 'src/index.ts', content: '...' }, { op: 'write', path: 'package.json', content: '...' }, { op: 'write', path: 'tsconfig.json', content: '...' } ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
atomicNoUse transactions (default: true)
parallelNoExecute in parallel (default: true)
operationsYesArray of operations
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses atomic rollback, automatic backups, parallel execution, and transaction support—valuable behavioral details beyond the schema. Still, it does not explain backup lifecycle or exact error/rollback semantics, so it is strong but not exhaustive.

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?

The description is well-structured with clear sections (Features, Operations, Parameters, Operation format, Examples) and is front-loaded with the main purpose. It is somewhat verbose, repeating atomic/parallel concepts, but every section contributes to usability.

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?

For a complex batching tool with no output schema, the description covers input semantics, operation types, atomic/parallel options, and provides examples. The main gap is that it does not describe the return value or result format, which would be especially important for read operations.

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

Parameters5/5

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

Even though the schema describes top-level parameters, the description adds crucial meaning through the operation format and examples. It clarifies how source/destination, content, oldText/newText, and path relate to each operation type, which is essential for correct invocation.

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 opens with 'Execute multiple file operations atomically,' which clearly states the verb, resource, and key scope. It distinguishes itself from sibling tools like efs_write/efs_edit by emphasizing multi-operation batching and atomicity.

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?

The description gives clear context through features and examples, implying use for multi-file operations and atomic refactoring. However, it does not explicitly contrast with single-operation sibling tools or state when not to use it, so it stops short of full alternatives guidance.

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/AesirKode/enhanced-filesystem-mcp'

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