Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

copy_files

Destructive

Copies files or folders into an existing destination folder without removing sources; skips existing items unless overwrite is enabled. If any source is missing, no copy runs.

Instructions

Copy files or folders into a destination folder; a folder is copied with everything in it, and the sources stay in place. To move instead, use move_files. dest_folder must already exist; it isn't created. With overwrite=false (default), items already at the destination are skipped and listed, and the rest are copied. If any source is missing, nothing is copied. A long copy keeps running on the NAS and returns a handle for file_task.

Input Schema

NameRequiredDescriptionDefault
pathsYesFiles or folders to copy (`/video/Downloads/clip.mkv`).
overwriteNoReplace items already at the destination (default false: they're skipped and listed).
dest_folderYesThe existing folder to copy into (`/video/Archive`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.1
    • addedInput schema / properties / dest_folder / description
      Added value: +"The existing folder to copy into (`/video/Archive`)."
    • addedInput schema / properties / overwrite / description
      Added value: +"Replace items already at the destination (default false: they're skipped and listed)."
    • addedInput schema / properties / paths / description
      Added value: +"Files or folders to copy (`/video/Downloads/clip.mkv`)."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_copy_filesOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.9/5.0
Behavior5/5

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

Goes well past the annotations: all-or-nothing validation ('If any source is missing, nothing is copied'), partial-success semantics under overwrite=false (skipped items are listed), and long-running behavior returning a handle for file_task. The description refines destructiveHint=true rather than fighting it — the default path destroys nothing.

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?

Five tight sentences, each carrying distinct operational information, with the core purpose and the move_files routing front-loaded. No filler and no restatement of the name.

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?

No output schema exists, and the description covers the return path (handle for file_task) plus batch outcomes (skipped-and-listed), so nothing an agent needs in order to call or follow up correctly is missing.

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 already 100%, so the baseline is 3; the description earns above that by explaining the consequence of overwrite's default ('items already at the destination are skipped and listed') and by reinforcing the existence precondition on dest_folder, which the schema only implies.

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?

States a specific verb and resource (copy files or folders into a destination folder) and pins the semantics that distinguish it from move: 'the sources stay in place' and folders copy recursively.

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

Usage Guidelines5/5

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

Explicitly names the alternative ('To move instead, use move_files') and adds preconditions to use: 'dest_folder must already exist; it isn't created.' It also explains what happens under each overwrite mode, so the agent knows which call shape suits which intent.

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