ha-nexus-agent

Overview Schema Source Related Servers Discussions Admin

List active repair issues

system_get_repairs

Read-onlyIdempotent

Lists active Home Assistant repair issues, surfacing deprecated config, broken integrations, or required migrations that need attention.

Instructions

List Home Assistant's active repair issues.

Calls the repairs/list_issues WebSocket command and projects each issue down to its id, domain, severity, breaks_in_ha_version, learn-more URL, translation key, and ignored/is_fixable flags.

Use when: surfacing deprecated config, broken integrations or required migrations that need attention. Not for: the full raw repair-issue payload with every field HA stores — this always returns the projected subset above. Returns: list of {issue_id, domain, severity, breaks_in_ha_version, learn_more_url, translation_key, ignored, is_fixable} dicts. Errors: raises RuntimeError if the underlying WebSocket call fails (e.g. auth or WS-level error).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.18.1Jun 19, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world. The description adds genuinely new behavior: the projected field subset, the specific WebSocket command, and error semantics (RuntimeError on auth/WS failure). Only minor gap is pagination/scale behavior, which is minor for a read-only list.

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-loaded purpose sentence, then labeled Use when / Not for / Returns / Errors blocks. Every sentence carries distinct information with no redundancy.

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?

An output schema exists, yet the description still summarizes the projected return fields and documents failure behavior, covering both success and error paths. Complete for a zero-argument read tool.

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

Parameters4/5

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

Zero parameters, so per the baseline this scores 4. The description correctly adds no parameter prose since there is nothing to configure.

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 (List) and resource (Home Assistant's active repair issues) and names the underlying operation (`repairs/list_issues`). An agent can clearly distinguish this from sibling listing tools like system_get_system_health or history_get_error_log.

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?

Explicit 'Use when:' clause gives the trigger scenario (deprecated config, broken integrations, migrations needing attention) and a 'Not for:' clause scopes out the raw full payload. Nothing about when to reach for this is left to inference.

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

Deploy Server