Skip to main content
Glama
j0hanz

filesystem-mcp

by j0hanz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Delete File

delete
Destructive

Permanently remove files, directories, or symlinks (up to 1000 per call). Non-empty directories require recursive confirmation; irreversible.

Instructions

Permanently delete one or more files, directories, or symlinks (max 1000 per call). This action is irreversible. Pass paths: [...] — there is no single-path form. Non-empty directories require recursive=true and additionally prompt the user to confirm each one, so the call returns without deleting anything until that confirmation comes back; a client that cannot prompt gets an error naming the alternative. Workspace root directories cannot be deleted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathsYesPaths to delete (max 1000); accepts files, directories, or symlinks
recursiveNoDelete directory contents recursively (required for non-empty directories)
ignoreIfNotExistsNoSilently succeed if a path does not exist instead of returning an error

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. Changed1 schema field changedv2.1.5
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": false,
-  "properties": {
-    "results": {
-      "description": "Per-path results ordered to match the input paths",
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "error": {
-            "additionalProperties": false,
-            "description": "Error details; present on failure",
-            "properties": {
-              "code": {
-                "type": "string"
-              },
-              "message": {
-                "type": "string"
-              },
-              "path": {
-                "type": "string"
-              },
-              "suggestion": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "code",
-              "message"
-            ],
-            "type": "object"
-          },
-          "path": {
-            "description": "Requested path",
-            "type": "string"
-          },
-          "value": {
-            "additionalProperties": false,
-            "description": "Delete outcome; present on success",
-            "properties": {
-              "deleted": {
-                "description": "True when the path was removed; false when the user chose Skip",
-                "type": "boolean"
-              }
-            },
-            "required": [
-              "deleted"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "path"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "summary": {
-      "additionalProperties": false,
-      "properties": {
-        "failed": {
-          "minimum": 0,
-          "type": "integer"
-        },
-        "succeeded": {
-          "minimum": 0,
-          "type": "integer"
-        },
-        "total": {
-          "minimum": 0,
-          "type": "integer"
-        }
-      },
-      "required": [
-        "total",
-        "succeeded",
-        "failed"
-      ],
-      "type": "object"
-    }
-  },
-  "required": [
-    "results",
-    "summary"
-  ],
-  "type": "object"
-}New value: +null
  3. Addedv2.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes well beyond that by disclosing irreversibility, the confirmation prompt for non-empty directories, the fact that deletion is deferred until confirmation, the error behavior for non-prompting clients, and workspace root protection. No contradiction with 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 dense but every sentence carries essential information, and the most critical facts (permanent deletion, max 1000, irreversibility) are front-loaded. The paragraph is appropriately sized for a destructive multi-option operation.

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 no output schema, the description covers the key behavioral consequences: what gets deleted, the max batch size, irreversibility, recursive and confirmation requirements, the client-prompting failure mode, and workspace root restrictions. An agent has enough information to use the tool safely and correctly.

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%, so the baseline is 3. The description adds value beyond the schema by explaining that there is no single-path form, that non-empty directories require recursive=true and trigger a confirmation flow, and that workspace root directories cannot be deleted. This enriches the semantics of both paths and recursive.

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 uses a specific verb ('Permanently delete') and names the exact resources ('files, directories, or symlinks'), plus a clear cap of 1000 per call. It also distinguishes itself from a hypothetical single-path form, leaving no ambiguity about what this tool does.

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 operational guidance: paths must be passed as an array, there is no single-path form, non-empty directories require recursive=true, and workspace roots cannot be deleted. It does not explicitly name sibling alternatives like move or rename as the right choice for non-deletion operations, but deletion intent is unambiguous.

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