Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Reload Core Components

ha_reload_core
Destructive

Reload Home Assistant configuration components without restarting, applying changes to automations, scripts, helpers, themes, or a single integration entry.

Instructions

Execute a Home Assistant configuration reload without a full restart.

Reloads specific configuration components so changes take effect without restarting Home Assistant — much faster than a full restart. Use it after editing automation/script YAML, adding YAML helpers, or changing customize.yaml or themes.

EXAMPLES:

  • ha_reload_core(target="automations")

  • ha_reload_core(entry_id="abc123")

If a Claude Desktop user gets a 4-minute timeout with no result on this call, read the target back before repeating it, and tell them to wait a few seconds before clicking the manual-approve button, as clicking it too quickly is known to cause hangs in Claude Desktop. This workaround is specific to Claude Desktop.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoWhat to reload: 'all', 'automations', 'scripts', 'scenes', 'groups', 'input_booleans', 'input_numbers', 'input_texts', 'input_selects', 'input_datetimes', 'input_buttons', 'timers', 'templates', 'persons', 'zones', 'core' (customize, packages) or 'themes'.all
entry_idNoReload a SINGLE config entry (one integration instance) instead of sweeping subsystems — the fast path after editing a custom component on disk. Pass it alone (leave target at 'all'); combining it with an explicit target is a validation error. Find the id via ha_get_integration.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv8.6.0
    • addedInput schema / properties / entry_id / description
      Added value: +"Reload a SINGLE config entry (one integration instance) instead of sweeping subsystems — the fast path after editing a custom component on disk. Pass it alone (leave target at 'all'); combining it with an explicit target is a validation error. Find the id via ha_get_integration."
    • addedInput schema / properties / target / description
      Added value: +"What to reload: 'all', 'automations', 'scripts', 'scenes', 'groups', 'input_booleans', 'input_numbers', 'input_texts', 'input_selects', 'input_datetimes', 'input_buttons', 'timers', 'templates', 'persons', 'zones', 'core' (customize, packages) or 'themes'."
  2. First observedv7.14.2

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the entry_id single-component fast path, the validation error when combining target and entry_id, and a Claude Desktop timeout/hang workaround. It does not explain *why* the call is destructive (e.g. what running automations are interrupted), which is the main remaining gap.

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

Conciseness3/5

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

The purpose and trigger conditions are front-loaded and tight, but the closing Claude Desktop paragraph is long, hedged and tangential to the tool's function ('read the target back before repeating it... clicking it too quickly is known to cause hangs'), diluting an otherwise efficient definition.

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

Completeness4/5

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

Covers what to reload, when to use it, two invocation modes, and a known client-side failure mode; an output schema exists so return values need no explanation. What's missing is the destructive consequence of reloads and any permission/auth prerequisites, given destructiveHint=true.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds invocation examples (target="automations", entry_id="abc123") that demonstrate the two mutually exclusive usage modes. It repeats the schema's mutual-exclusion note rather than adding new constraint detail, keeping it out of 5 territory.

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 (Home Assistant configuration components) and immediately distinguishes itself from ha_restart by noting it avoids a full restart. An agent can tell it apart from the many sibling config setters/getters without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete trigger conditions: after editing automation/script YAML, adding YAML helpers, or changing customize.yaml or themes, and contrasts it with a full restart as 'much faster'. It lacks an explicit exclusion rule (e.g. when ha_restart is actually required), so it falls just short of a 5.

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