Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Restart HA Core

supervisor_restart_core
DestructiveIdempotent

Restart Home Assistant Core via the Supervisor after explicit confirmation. Use for Supervisor-managed installations; requires confirm=True and interrupts Core until restart completes.

Instructions

Restart Home Assistant Core through the Supervisor after an explicit confirmation.

Calls POST /core/restart. WARNING: causes downtime for HA Core (and everything depending on it) until it comes back up. Without confirm=True nothing is restarted.

Use when: Core needs restarting on a Supervisor install specifically. Not for: the equivalent call via HA's own service — use system_restart_ha; for rebooting the whole host — use supervisor_restart_host. Returns: Supervisor's restart-job result when confirmed. Errors: returns {"error": "confirmation_required", "message": ..., "action": ...} when confirm is false; {"error": "SUPERVISOR_TOKEN not set — Nexus must run as HA add-on for Supervisor API"} when the token env var is missing. Limits: requires confirm=True; interrupts Core until it restarts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoSet true to actually restart Core. False (default) performs no action.

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 restart Core. False (default) performs no action."
  2. 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 it destructive and non-read-only, but the description adds important operations context: downtime impact on Core and dependents, the confirmation requirement, specific error payloads, and a token prerequisite. This goes well beyond what the annotations convey.

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?

The definition is front-loaded with the core action and warning, then efficiently structured into 'Use when', 'Not for', 'Returns', 'Errors', and 'Limits'. Every sentence adds information an agent needs to call the tool correctly.

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?

For a destructive Supervisor-level restart tool, the description covers when to use it, when not to, return behavior, error cases, and side effects. With an output schema present and annotations covering safety, this is complete enough for correct invocation.

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 `confirm` parameter is already well described in the schema. The description reinforces that `confirm=True` is required and that without it nothing is restarted, but adds little new semantic content beyond what the schema provides.

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: restart Home Assistant Core through the Supervisor. It explicitly distinguishes from the two closest siblings by explaining it is for Supervisor installs specifically and naming `system_restart_ha` and `supervisor_restart_host` as alternatives.

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 'Use when' and 'Not for' sections, directing the agent to `system_restart_ha` for the HA service equivalent and `supervisor_restart_host` for a host reboot. The conditions that select this tool versus alternatives are fully specified.

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