Skip to main content
Glama

Dateien löschen

fs_delete
Destructive

Löscht Dateien aus dem Workspace. Die Version davor bleibt erhalten und lässt sich zurückholen.

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": {
      "website": "<website>",
      "paths": "<paths>"
    },
    "name": "fs_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
messageNoWas diese Änderung bewirkt, für die Versionsliste
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true; the description adds genuinely new behavior by stating the prior version is retained and can be recovered, which tells the agent the delete is soft/reversible. It stops short of saying how recovery happens (which tool), whether the delete is atomic across the paths array, or whether anything is permanently lost.

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?

Two short sentences, no filler, with the primary effect front-loaded and the reversibility note immediately after.

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

Completeness3/5

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

For a destructive 3-parameter tool with no output schema, the definition covers the core effect and recoverability but omits how recovery is performed, the result of a batch delete over multiple paths, and any preconditions on the paths argument.

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 coverage is 67% and the field descriptions for paths and website are already detailed, so the schema does most of the work. The description adds no parameter-level meaning and even uses "Workspace" where the schema speaks of a "website", a slight terminology mismatch.

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

Purpose4/5

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

The description names a specific verb and resource ("Löscht Dateien aus dem Workspace") and scopes it to the workspace, which is enough to separate it from fs_read/fs_write. It does not explicitly name a contrasting sibling (e.g. rollback), so it falls short of a 5.

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?

Deletion is implied by the verb and the schema's required paths/website, but there is no explicit guidance on when to delete instead of overwrite with fs_write, or how to reach rollback to restore. Usage is inferable but never stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources