Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Stop Home Assistant

system_stop_ha
DestructiveIdempotent

Stops Home Assistant after explicit confirmation, taking it fully offline for host maintenance. Requires confirm=true and a manual restart to bring it back online.

Instructions

Stop Home Assistant after an explicit confirmation.

Calls the homeassistant.stop service. Unlike a restart, nothing brings the instance back automatically — a manual restart is required. Without confirm=True nothing is stopped; the call only returns a safety prompt.

Use when: HA needs to be taken fully offline, e.g. before host maintenance. Not for: a temporary interruption that comes back on its own — use system_restart_ha. Returns: the homeassistant.stop service-call result when confirmed, otherwise a confirmation prompt. Errors: returns {"error": "confirmation_required", "message": ..., "action": ...} when confirm is false. Limits: requires a manual restart to bring HA back online; requires confirm=True.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true to actually stop HA. False (default) performs no action and instead returns a confirmation prompt.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / confirm / description
      Added value: +"Set true to actually stop HA. False (default) performs no action and instead returns a confirmation prompt."
  2. Changed1 schema field changedv0.18.1
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "type": "boolean"
+}
  3. First observedv0.3.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as destructive, non-read-only, idempotent, and closed-world, but the description adds critical behavioral context: confirmation is required, no automatic restart follows, the exact error shape when confirmation is missing, and the manual restart requirement.

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

Conciseness5/5

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

Front-loads the core action and confirmation requirement, then uses clearly labeled sections for use, non-use, returns, errors, and limits. Despite covering many points, each line earns its place for a destructive system-level tool.

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 still explains the return behavior and error case, which is useful. Combined with explicit limits and alternatives, it gives an agent everything needed to invoke this destructive tool safely and 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 schema already documents the `confirm` parameter and its default. The description reinforces that `confirm=True` is required but adds little semantic detail beyond the schema, so the baseline 3 is appropriate.

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 and resource (Stop Home Assistant) and explicitly distinguishes it from restart by noting that nothing brings the instance back automatically. The service name `homeassistant.stop` further clarifies the operation.

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?

Provides explicit when-to-use guidance ('HA needs to be taken fully offline, e.g. before host maintenance') and when-not-to-use guidance ('Not for: a temporary interruption that comes back on its own'), naming the alternative `system_restart_ha`.

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