Skip to main content
Glama
Claude Free Code MCP

Claude Free Code MCP

by ImIpscanning

delete_path

Destructive

Deletes a regular file with an undo snapshot or an empty folder, requiring approval and blocking recursive deletion.

Instructions

Delete a regular file (with undo snapshot) or an EMPTY folder. Requires approval; recursive deletion is disabled.

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": {
      "file": "<file>"
    },
    "name": "delete_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesFile or empty folder to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, and the description adds substantial behavior beyond that: a snapshot is taken enabling undo, an approval step gates execution, and recursion is disabled so a non-empty folder will not be traversed. Those are the exact facts an agent needs before invoking a destructive operation.

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 with zero filler, front-loading the operation, the undo guarantee, and the constraint. Nothing is repeated from the schema beyond what is needed to set scope.

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

Completeness4/5

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

For a single-parameter destructive tool with no output schema, the definition covers safety, scope, and undo. It stops short of saying what is returned (snapshot handle or confirmation) or what happens on a non-empty folder (error vs refusal), minor residual gaps.

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% and there is only one parameter, so the schema already documents it. The description restates that the target may be a file or empty folder but adds no new syntax, path-format, or resolution detail, so the baseline 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?

States a specific verb (delete) and precise scope: a regular file, or an EMPTY folder. The parenthetical '(with undo snapshot)' and the explicit exclusion of recursive deletion let an agent distinguish this from a general removal tool without reading the schema.

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?

Clearly gives the conditions of use (file or empty folder only, recursive deletion disabled, approval required), which implicitly rules out non-empty directory trees. It does not name any sibling as the alternative for recursive or bulk removal, so routing between tools is left slightly inferential.

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