Delete a file or directory from your persistent workspace. Free. Use responsibly.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | Relative path inside the workspace to delete | |
| agent_id | Yes | Your agent identifier |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already signal destructiveness (destructiveHint=true, readOnlyHint=false). The description adds context like 'persistent workspace' and 'Free,' but does not disclose specifics such as permanence or effects on directories. It does not contradict the annotations.
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 description is concise and front-loads the purpose. However, 'Free.' and 'Use responsibly' are filler that add little meaningful information. Still, it is appropriately sized for a simple delete operation.
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 simple delete tool with no output schema, the description is adequate given the annotations, but it lacks explicit statements about permanence or directory deletion behavior. It is sufficient for basic usage yet leaves gaps for a destructive action.
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?
The input schema includes descriptions for both parameters (path and agent_id), achieving 100% coverage. The description does not add parameter-level detail beyond the schema, but the schema already fully documents the parameters, warranting a baseline score of 3.
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?
The description uses the specific verb 'delete' and identifies the resource as 'a file or directory from your persistent workspace.' This clearly distinguishes it from sibling tools like workspace_list and workspace_status, which are read 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?
The description provides no explicit guidance on when to use this tool versus alternatives. 'Use responsibly' is a generic caution, not a usage rule. It does not mention prerequisites, irreversibility, or situations where another tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes, but there is potential confusion between 'decision' and 'reason', both offering advisory output. Also, 'review', 'witness', 'prove', and 'verify_proof' overlap in the proofs space, though descriptions differentiate them. Overall, an agent can disambiguate with careful reading.
All tool names use lowercase and underscores (snake_case), which is consistent. However, the verbs vary: some are imperative (e.g., 'browse', 'execute'), while others are nouns (e.g., 'signals', 'ledger'), breaking a strict verb_noun pattern. Overall, the naming is readable and mostly predictable.
With 30 tools, the surface is too large for a well-scoped server. Many functions could be separated (e.g., memory, workspace, feedback, marketplace). This excess makes it harder for an agent to navigate and select the right tool quickly.
The tool set covers core CRUD for memory and workspace, plus feedback, marketplace purchase, bounties, and verification. However, there is no tool to list or search marketplace listings, and workspace creation is only implicit via 'execute'. These gaps hinder fluid workflows.
