Skip to main content
Glama
Sign In
fast-filesystem-mcp

fast-filesystem-mcp

by efforthye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

fast_batch_file_operations

Execute batch file operations including copy, move, delete, and rename across multiple files. Control overwrite, error handling, and preview changes before execution.

Instructions

Performs batch operations on multiple files

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

Input Schema

NameRequiredDescriptionDefault
operationsYesList of batch operations
stop_on_errorNoStop on error
dry_runNoPreview without actual execution
create_backupNoCreate backup before changes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.0.0
    • changedInput schema / properties / create_backup / description
      Previous value: -"변경 전 백업 생성"New value: +"Create backup before changes"
    • changedInput schema / properties / dry_run / description
      Previous value: -"실제 실행 없이 미리보기"New value: +"Preview without actual execution"
    • changedInput schema / properties / operations / description
      Previous value: -"일괄 작업 목록"New value: +"List of batch operations"
    • changedInput schema / properties / operations / items / properties / destination / description
      Previous value: -"대상 경로 (copy, move, rename용)"New value: +"Destination path (for copy, move, rename)"
    • changedInput schema / properties / operations / items / properties / operation / description
      Previous value: -"작업 유형"New value: +"Operation type"
    • changedInput schema / properties / operations / items / properties / overwrite / description
      Previous value: -"덮어쓰기 허용"New value: +"Allow overwrite"
    • changedInput schema / properties / operations / items / properties / source / description
      Previous value: -"원본 경로"New value: +"Source path"
    • changedInput schema / properties / stop_on_error / description
      Previous value: -"에러 발생시 중단"New value: +"Stop on error"
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations exist, and the description fails to disclose critical behaviors like dry-run preview, backup creation, error handling, or atomicity. The schema contains these fields (stop_on_error, dry_run, create_backup) but the description does not surface them.

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 a single short sentence, which is very concise. However, the brevity sacrifices informative value, so it earns a 4 rather than a 5.

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

Completeness2/5

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

Given the complexity of batch operations and the absence of output schema, the description omits essential details like return behavior, result format, execution order, and error reporting. It is missing information that would help an agent use the tool correctly.

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 schema already documents parameters. The description adds no extra parameter meaning, but the baseline is 3 due to high coverage. It provides minimal context for the overall operation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Performs batch operations on multiple files' is generic and does not specify the supported operations (copy, move, delete, rename) visible in the schema. It conveys batch processing but lacks specificity, making it only slightly above a tautology.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this batch tool versus the many sibling single-operation tools (e.g., fast_copy_file, fast_delete_file). There is no mention of trade-offs or prerequisites.

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