Skip to main content
Glama
j0hanz

filesystem-mcp

by j0hanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Move or Copy Files

move
Destructive

Relocate or copy files/directories in batches by specifying source and destination. Parent dirs are auto-created; overwrites require confirmation, and copy mode can skip prompts.

Instructions

Move, rename, or copy files and directories to explicit destination paths (max 100 operations per call). Pass moves: [{ source, destination }] — there is no single-pair form. Parent directories are created automatically. Set copy=true to copy instead of move (sources are kept). An existing destination prompts the user to confirm the overwrite, so the call returns without moving anything until that confirmation comes back; copy=true with overwrite=true skips the prompt, move has no such bypass. Self-moves are silently skipped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
copyNoCopy instead of move; sources are left in place
movesYesOperations to perform (max 100)
overwriteNoCopy mode only: overwrite existing destinations without confirmation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.4.1
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  2. Addedv2.0.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations indicate destructiveHint=true and readOnlyHint=false, so the description goes beyond by disclosing critical behaviors: overwrite confirmation prompts, the lack of a bypass for move operations, self-move skipping, and the effect of copy=true with overwrite=true. This adds significant context beyond the annotations.

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?

The description is concise and front-loaded with the core purpose, then efficiently covers key behaviors in a single paragraph. There is no fluff; every sentence contributes essential information, and the structure flows logically from purpose to usage details.

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

Completeness5/5

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

Given the tool's complexity (array of operations, max 100, overwrite logic, copy mode), the description covers all necessary aspects for correct invocation: format, limits, parent directory handling, confirmation behavior, and edge cases like self-moves. No output schema exists, so return values are not required. The description is complete.

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

Parameters4/5

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

Schema coverage is 100%, with each parameter described. The description adds value by explaining the interaction between copy and overwrite, the array-only format, and the absence of a single-pair form, which the schema does not convey. This goes beyond mere repetition and clarifies parameter semantics.

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 clearly states the tool moves, renames, or copies files and directories to explicit paths. It distinguishes from siblings by focusing on move/copy operations, while siblings like create, delete, and edit have different purposes. The mention of 'max 100 operations' and the array format adds specificity.

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?

The description provides detailed usage instructions, such as the mandatory array format, parent directory auto-creation, and copy vs. move behavior. However, it does not explicitly state when to choose this tool over alternatives (e.g., delete vs. move, create vs. copy), leaving the agent to infer the appropriate context from the tool name and purpose.

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