Skip to main content
Glama

fs_delete

DestructiveIdempotent

Delete a file or directory. Directory deletes are recursive — all children are removed. Archived versions are also cleaned up.

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": {
      "project_id": "<project_id>",
      "path": "<path>"
    },
    "name": "fs_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesFull path with leading slash
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known; the description adds real value beyond that by stating that directory deletes recurse to all children and that archived versions are purged too — a non-obvious side effect. It omits what happens on a nonexistent path and whether any confirmation is required.

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?

Three short sentences, each carrying distinct information, with the destructive recursion warning front-loaded directly after the basic purpose.

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 two-parameter destructive tool with full schema coverage and annotations carrying the safety hints, the description supplies everything needed to call it correctly: scope of deletion, recursion, and archived-version cleanup. No output schema is needed here.

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 100%, and the schema itself explains the path format and the project_id resolution rules in detail. The description adds no parameter-level meaning (e.g., whether a trailing slash changes behavior), so baseline 3 applies.

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?

States a specific verb and resource ("Delete a file or directory") plus scope detail: recursion over children and cleanup of archived versions. It clearly distinguishes a deletion tool from the fs_read/fs_write/fs_stat siblings, though it does not name any alternative for non-destructive operations.

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?

Usage is implied by the verb rather than explained; there is no explicit when-to-use or when-not-to-use guidance, and no mention of prerequisites such as confirming a path with fs_stat first. The recursion note is the only steer on the consequence of choosing a directory path.

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