Deletes a specified file or directory on a 1Panel server, with an optional force flag. Use it to remove unwanted files or clear storage during server administration.
Delete file or directory
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| forceDelete | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It conveys a destructive operation but omits irreversibility, permission requirements, forceDelete semantics, and whether deletion goes to a recycle bin.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The phrase is concise, front-loaded, and free of filler. However, it is too terse for a destructive tool with an undocumented forceDelete parameter, leaving necessary structure and safety context unstated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, 0% schema description coverage, and two parameters, the description is far too sparse. It does not explain parameter behavior or destructive consequences, making it inadequate for safe invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for two parameters. The description does not explain the path format or the optional forceDelete boolean, so it fails to compensate for the missing schema documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Delete file or directory'), distinguishing it from siblings like delete_website, delete_database, and delete_backup. However, it adds no scope or context about the target filesystem or alternatives such as recycle-bin operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance, no exclusions, and no alternative tools named. The description implies deletion is the purpose but does not say when to prefer this over moving, renaming, or other file operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.