Stop a running app and delete its containers while preserving data. Use to uninstall applications without losing stored information.
Stop an installed app and remove its containers. Data is preserved.
| 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?
Given no annotations, the description discloses key behavioral trait: data is preserved during removal. However, it does not specify authorization needs, reversibility, or side effects on other app states.
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 succinct sentences without redundancy, front-loading the action and then the key side effect. Every word earns its place.
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 tool with no output schema, the description covers the core functionality and the important data preservation detail. It is nearly complete but could explicitly mention the Docker context given sibling tools like 'docker_stop'.
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 has 100% coverage with one parameter 'app' described as 'App name'. The description adds no additional meaning beyond the schema, achieving baseline 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 clearly states the tool stops an installed app and removes its containers, with data preservation. It uses specific verb ('stop', 'remove') and resource ('installed app', 'containers'), and distinguishes from siblings like 'install_app' (installs) and 'install_purge' (likely removes data).
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 is provided on when to use this tool versus alternatives (e.g., 'install_purge' or 'docker_stop'). It simply describes the action without context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.