Skip to main content
Glama
Sign In
mcp-synology

mcp-synology

by cmeans
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_files

Destructive

Delete exact file and folder paths, recursively by default; items go to the recycle bin when available, otherwise deletion is permanent.

Instructions

Delete files or folders. A folder is deleted with everything in it (recursive, default true). On a share with a recycle bin, deleted items go to the bin: list_recycle_bin shows them and restore_from_recycle_bin brings them back. Without a bin, and for anything inside a bin (/<share>/#recycle), deletion is permanent. Paths are exact, not wildcard patterns, and if any path is missing nothing is deleted. A long delete keeps running on the NAS and returns a handle for file_task.

Input Schema

NameRequiredDescriptionDefault
pathsYesExact paths of the files or folders to delete (`/video/Downloads/old.mkv`); wildcards aren't expanded.
recursiveNoDelete a folder with everything in it (default true); with `false`, a folder that isn't empty is refused and kept.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.1
    • addedInput schema / properties / paths / description
      Added value: +"Exact paths of the files or folders to delete (`/video/Downloads/old.mkv`); wildcards aren't expanded."
    • addedInput schema / properties / recursive / description
      Added value: +"Delete a folder with everything in it (default true); with `false`, a folder that isn't empty is refused and kept."
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "tool_delete_filesOutput",
-  "type": "object"
-}New value: +null
  2. Addedv0.7.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark this as destructive, and the description adds substantial context: recycle-bin routing, permanent deletion inside a bin, recursive default behavior, all-or-nothing path handling, and an async handle for long deletes. These details go well beyond the annotations without contradicting them.

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 action and recursive behavior are front-loaded, and each subsequent sentence adds a distinct operational fact needed for a destructive tool. There is minor overlap with the schema on exact paths and recursive behavior, but no filler.

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?

For a destructive tool with annotations but no output schema, the description covers the essential behavior an agent needs: recycle bin versus permanent deletion, recursive folder handling, atomicity when paths are missing, and async handling for long operations. Nothing critical is omitted.

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 exact paths and the recursive default/refusal behavior. The description reinforces those points but adds little parameter-specific syntax or meaning beyond the schema, so the baseline of 3 applies.

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 a specific verb and resource ('Delete files or folders') and immediately distinguishes the recursive folder behavior. It is clearly distinct from siblings such as delete_download and file_task.

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?

It explains the conditions that determine whether a deletion is recyclable or permanent, notes that paths are exact and that any missing path aborts the whole delete, and points to list_recycle_bin, restore_from_recycle_bin, and file_task. It does not explicitly say when to prefer delete_files over delete_download, but the operational context is clear.

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