Remove a dataspace and all its associated documents from Locus to free up storage and avoid data clutter. Use when you need to permanently delete an entire space.
Delete a dataspace and all its documents from Locus
| Name | Required | Description | Default |
|---|---|---|---|
| space | Yes | Name of the dataspace to delete |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing destructiveness. It clearly states that the dataspace and all its documents are deleted, which is the key behavioral trait. However, it does not mention irreversibility, permissions, or other side effects.
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 a single concise sentence that front-loads the action and main consequence. Every word earns its place with no redundancy or filler.
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 one-parameter destructive tool with no output schema, the description covers the essential behavior: what is affected (dataspace and all documents). It omits minor details like irreversibility or return behavior, but these are not critical for basic selection and 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?
The input schema fully describes the only parameter, 'space', as 'Name of the dataspace to delete' with 100% coverage. The description adds no additional meaning, format, or examples beyond what the schema already provides, so the baseline of 3 applies.
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 a specific verb ('Delete'), specifies the resource ('a dataspace'), and adds the cascading scope ('all its documents'). This clearly distinguishes it from sibling delete_document and from list_spaces/create_space.
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 phrase 'and all its documents' implies this tool is for deleting an entire dataspace rather than a single document, but there is no explicit when-to-use or when-not-to-use guidance. The distinction from delete_document is only implicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.