ha_uninstall_addon
Remove a Home Assistant add-on permanently from your system by specifying its slug.
Instructions
Uninstall a Home Assistant add-on
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Add-on slug to uninstall |
Remove a Home Assistant add-on permanently from your system by specifying its slug.
Uninstall a Home Assistant add-on
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Add-on slug to uninstall |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description only states the basic action. It does not disclose potential effects like data loss or prerequisite conditions, which are important for a destructive operation.
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, efficient sentence with no superfluous information.
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 straightforward tool with one parameter and no output schema, the description is minimally viable but lacks context on confirmation, reversibility, or impact on other add-ons.
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 clear parameter name and description. The tool description adds no additional meaning beyond what the schema provides, warranting a baseline score of 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 'Uninstall a Home Assistant add-on' clearly states the action (uninstall) and resource (add-on), distinguishing it from siblings like ha_install_addon, ha_start_addon, etc.
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., ha_stop_addon for temporary stopping), nor prerequisites or side effects.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarahkon/hass-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server