Permanently remove an AnythingLLM workspace by slug, including its embeddings, to clean up unused or obsolete data.
Delete a workspace by slug. DESTRUCTIVE -- removes the workspace and its embeddings.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes |
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It does add meaningful behavioral context: the operation is destructive and cascades to the workspace's embeddings, which is non-obvious. However, it omits irreversibility, required authorization, and failure behavior for unknown slugs.
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?
Two tight sentences with zero filler. The destructive warning is front-loaded immediately after the purpose statement, which is exactly where an agent needs it.
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 one-parameter destructive mutation with no annotations and no output schema, the description covers the essentials of what and how harmful, but leaves gaps around irreversibility, permissions, and error cases that an agent authorizing/planning the call would want.
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 the single `slug` parameter, but the description clarifies that the slug is the workspace identifier used for lookup. That is real but minimal added meaning; no format or example is given.
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 (Delete) and resource (workspace) plus the lookup key (by slug). An agent can distinguish this from get_workspace, update_workspace, and create_workspace purely from the verb, and from list_workspaces by the singular-resource scope.
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 choose deletion versus alternatives, no prerequisites, no confirmation or permission requirements. The only signal is the DESTRUCTIVE marker, which is a warning rather than usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.