Stop an app and permanently remove its containers, config, and volumes. Use when you need to completely purge an installation—back up first if data matters.
Stop an installed app and delete all data including containers, config, and volumes. Nothing here restores it and no backup is taken first: take one before calling if the data matters
| 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 provided, the description carries the full burden and does exceptionally well. It discloses destructive behavior, enumerates what is deleted (containers, config, volumes), states irreversibility, and explicitly notes no automatic backup is taken.
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 efficient sentences front-load the core action and then add a critical safety warning. Every phrase earns its place, with no redundant 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 operation with no output schema, the description is complete: it states the action, scope of deletion, irreversibility, and the backup prerequisite. Nothing essential is missing for an agent to invoke it correctly.
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% with the 'app' parameter already described as 'App name'. The description adds minimal extra meaning by noting the app must be an installed app, but it does not need to compensate for any schema gap.
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 ('Stop', 'delete') and a concrete resource ('installed app' and all data including containers, config, volumes). Clearly distinguishes itself from sibling tools like install_uninstall by emphasizing irreversible data deletion.
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?
Provides clear context for when to use the tool: when complete removal of an app and its data is intended. It warns to take a backup first if data matters, but does not explicitly name or exclude alternatives such as install_uninstall.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.