Skip to main content
Glama

Delete Recursive

delete_recursive

Recursively deletes a specified file or directory tree, removing nested contents in one operation; use with caution because the deletion is permanent.

Instructions

Recursively delete a file or directory tree. Use with caution.

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

Input Schema

NameRequiredDescriptionDefault
pathYesRelative or absolute path to the file/directory.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden for a destructive operation. It discloses recursion and a caution, but not irreversibility, whether deletion is permanent or recoverable, permission requirements, or behavior on partial failure/symlinks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short, front-loaded sentences with no redundancy. 'Use with caution' is generic but does put the risk next to the action rather than burying it.

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

Completeness2/5

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

An output schema exists so return values need no explanation, but for an irreversible recursive delete with zero annotations the definition should spell out consequences and safety expectations. The current text leaves an agent without the context needed to invoke it responsibly.

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?

Only one parameter exists and the schema documents it at 100% coverage ('Relative or absolute path to the file/directory'), so the baseline is high. The description adds the useful nuance that the path may point at a whole tree, not just a leaf.

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') plus the key differentiator 'recursively' against the sibling delete_path, and clarifies the target can be a file or a directory tree. It stops short of naming delete_path explicitly, so an agent must infer the pairing.

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

Usage Guidelines2/5

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

'Use with caution' is a warning, not usage guidance. There is no statement of when to prefer this over the sibling delete_path, no preconditions, and no case where recursion should be avoided.

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