Skip to main content
Glama

Stop an add-on

supervisor_stop_addon
DestructiveIdempotent

Stop a running Home Assistant add-on without uninstalling it, taking services like an MQTT broker offline until started again. Refuses to stop Nexus's own add-on.

Instructions

Stop a running add-on.

Calls POST /addons/<slug>/stop. The add-on — e.g. an MQTT broker other integrations depend on — becomes unavailable until started again. Refuses to run at all against nexus's own add-on (by its real slug or the literal alias Supervisor resolves to the caller itself): nexus stopping itself would cut off the very connection carrying this call, with no guarantee the response ever comes back, and — unlike supervisor_restart_addon — leaves nexus down until someone starts it again some other way.

Use when: taking one add-on offline without uninstalling it. Not for: removing it entirely — use supervisor_uninstall_addon; for bringing it back — use supervisor_start_addon; for a brief restart of nexus itself — use supervisor_restart_addon instead, which is allowed. Returns: Supervisor's stop-job result. Errors: {"error": "invalid_slug"} for a bad slug; {"error": "self_addon_stop_blocked", "message": ...} when slug is nexus's own add-on; {"error": "SUPERVISOR_TOKEN not set — Nexus must run as HA add-on for Supervisor API"} when the token env var is missing; {"error": "HTTP <status>", "detail": ...} if the slug is unknown. Limits: interrupts the add-on's availability, and anything depending on it, until it is started again.

Input Schema

NameRequiredDescriptionDefault
slugYesAdd-on slug to stop, e.g. from `supervisor_list_addons`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / slug / description
      Added value: +"Add-on slug to stop, e.g. from `supervisor_list_addons`."
  2. First observedv0.3.0

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover destructive/idempotent/readOnly status, but the description adds critical behavior: the add-on and dependents become unavailable until started again, stopping nexus's own add-on is blocked, the token prerequisite, error payloads, and limits. No annotation contradiction is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then organized into effect, use/not-for, returns, errors, and limits. It is long but most sentences earn their place; some error detail could be tightened.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Even though an output schema exists, the description gives a useful return summary and enumerates the important error cases, token prerequisite, self-call restriction, and availability impact. An agent has enough information to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single slug parameter is already documented in the schema. The description reinforces where slugs come from and mentions invalid_slug/self-add-on errors, but adds little parameter syntax or format detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Stop a running add-on.' It also names the endpoint and effect, and clearly distinguishes itself from start, restart, and uninstall siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly gives a 'Use when' condition and a 'Not for' section naming alternatives: uninstall for removal, start for bringing it back, and restart for a brief restart of nexus itself. The routing guidance is complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools