Stop an installed app and remove its containers, preserving the app directory and volumes on disk for later reinstallation or cleanup.
Stop an installed app and remove its containers. The app directory and its volumes stay on disk; install_purge is the one that deletes them
| Name | Required | Description | Default |
|---|---|---|---|
| app | Yes | App name |
Changes observed during successful MCP inspections.
v0.10.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses what is removed (containers), what is preserved (app directory and volumes), and points to install_purge for destructive deletion. This is genuinely informative, though it does not address reversibility or side effects beyond removal.
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 one information-dense sentence with no filler. The key behavioral distinction is front-loaded, and the alternative tool is mentioned without unnecessary elaboration.
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 single-parameter operation, the description provides enough to understand the action, what persists, and which sibling covers the destructive case. It leaves out return values or error behavior, but that is not critical given the tool's simplicity.
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 coverage is 100% and the only parameter 'app' is already described as 'App name'. The description adds little parameter-level detail, but none is needed for this simple one-parameter tool, so the baseline of 3 is appropriate.
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 clearly states a specific behavior: stop an installed app and remove its containers. It also distinguishes this tool from install_purge by noting that the app directory and volumes remain on disk, making the scope of the operation unambiguous.
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 gives strong context by naming install_purge as the alternative that deletes app directories and volumes, implying this tool is for cleanup while preserving data. It does not explicitly say 'use this when...' but the contrast is clear enough for an agent to choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.