ha-nexus-agent

Overview Schema Source Related Servers Discussions Admin

Reload helper entities from config

helpers_reload_helpers

Idempotent

Reload all helper domains at once to apply YAML changes without restarting Home Assistant. Reports which domains reloaded and captures each failure per domain.

Instructions

Reload every helper domain's entities from configuration in one call.

Calls <domain>.reload over HTTP for each of input_boolean, input_number, input_text, input_select, input_datetime, counter, timer in turn; a domain whose reload call raises is skipped but its error is captured rather than silently dropped.

Use when: applying YAML changes across several helper domains without restarting Home Assistant. Not for: reloading one specific domain — use services_reload_config. Returns: {"reloaded": [...], "failed": {domain: message}} — combined list of states changed across every domain that reloaded successfully, plus a per-domain map of the error message for every domain whose reload call raised. Errors: a domain's failure never raises out of this call; instead its exception message is recorded under failed[<domain>] so the caller can tell which domain, if any, did not reload.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.25.1Oct 4, 2026

addedOutput schema / additionalProperties
```
Added value: +true
```

removedOutput schema / properties

Removed value: -{
-  "result": {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / required
```
Removed value: -[
-  "result"
-]
```
removedOutput schema / x-fastmcp-wrap-result
```
Removed value: -true
```

First observedv0.3.0May 3, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds valuable behavior beyond that: per-domain sequential HTTP calls, partial-failure semantics (a failing domain is skipped, its error captured, never raised), which is not derivable from annotations or schema.

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?

Well front-loaded: the one-line summary comes first, then domain list, then Use when / Not for / Returns / Errors. Slightly verbose in restating the return shape and error map, which an output schema already covers, but every sentence carries actionable content.

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?

Given zero params, an existing output schema, and annotations covering the safety profile, the description still fills the remaining gaps: scope (all helper domains), routing (vs services_reload_config), and the non-raising partial-failure contract. Nothing an agent needs to call it correctly is missing.

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 input parameters, so the baseline is 4. The description helpfully frames that the call is parameterless by enumerating the fixed set of domains it operates on, leaving nothing ambiguous about what the agent must supply.

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 (reload) and resource (every helper domain's entities), and enumerates the exact domains covered. It is clearly distinguishable from the sibling services_reload_config (single domain) and helpers_list_helpers (read).

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: applying YAML changes across several helper domains without restarting Home Assistant' and 'Not for: reloading one specific domain — use services_reload_config', naming the alternative and the condition that selects it.

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

Deploy Server