delete_file
Delete a file or directory from the filesystem using a specified path. Optionally remove directories recursively.
Instructions
Delete file
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| recursive | No |
Delete a file or directory from the filesystem using a specified path. Optionally remove directories recursively.
Delete file
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| recursive | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must disclose behavior. Only states 'Delete file' without noting irreversibility, behavior on directories, or path existence requirements.
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?
Extremely brief (2 words), but this is under-specification rather than conciseness. The description is too short to be useful for a tool with parameters.
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?
For a tool with two parameters and no output schema, the description fails to explain essential details like recursive deletion, prerequisites, or return behavior. Incomplete.
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?
Description gives no information about parameters 'path' and 'recursive'. Schema coverage is 0%, so agent has no clue what 'recursive' means or how to use the tool correctly.
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?
Clearly states verb and resource ('Delete file'), but doesn't clarify that it can also delete directories recursively. The purpose is understood but lacks nuance.
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 guidance on when to use this tool versus sibling file operation tools like copy_file, move_file, or write_file. No mention of alternatives or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/FutureAtoms/agentic-control-framework'
If you have feedback or need assistance with the MCP directory API, please join our Discord server