MCP-Delete
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delete_fileC | Delete a file at the specified path (supports both relative and absolute paths) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is singular and clearly defined.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'delete_file' follows a clear verb_noun pattern.
One tool is too few for a server named 'MCP-Delete', which suggests a broader deletion domain. A single file deletion tool feels thin and incomplete for the implied scope.
The server name implies deletion operations, but only file deletion is covered. There are significant gaps, such as deleting directories, database entries, or other resources, which will likely cause agent failures.