Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

Reload Core Components

ha_reload_core
Destructive

Reload specific Home Assistant configuration components—automations, scripts, scenes, helpers, and more—without restarting the entire instance. Use targets like 'all' or a specific entry_id for quick updates.

Instructions

Reload Home Assistant configuration without full restart.

This tool reloads specific configuration components, allowing changes to take effect without restarting the entire Home Assistant instance. This is much faster than a full restart.

Parameters:

  • target: What to reload. Options:

    • "all": Reload all reloadable components

    • "automations": Reload automation configurations

    • "scripts": Reload script configurations

    • "scenes": Reload scene configurations

    • "groups": Reload group configurations

    • "input_booleans": Reload input_boolean helpers

    • "input_numbers": Reload input_number helpers

    • "input_texts": Reload input_text helpers

    • "input_selects": Reload input_select helpers

    • "input_datetimes": Reload input_datetime helpers

    • "input_buttons": Reload input_button helpers

    • "timers": Reload timer helpers

    • "templates": Reload template sensors/entities

    • "persons": Reload person configurations

    • "zones": Reload zone configurations

    • "core": Reload core configuration (customize, packages)

    • "themes": Reload frontend themes

  • entry_id: 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 its "all" default); combining it with an explicit target is a validation error. Find the id via ha_get_integration.

Example Usage:

# Reload just automations after editing
ha_reload_core(target="automations")

# Reload all configurations
ha_reload_core(target="all")

# Reload input helpers after adding new ones
ha_reload_core(target="input_booleans")

When to Use:

  • After editing automation/script YAML files

  • After adding new input helpers via YAML

  • After modifying customize.yaml

  • After theme changes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNoall
entry_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already indicate destructiveHint=true, so the description adds value by detailing what reload actions are available (target options) and the special behavior of entry_id (fast path for single integration). It does not repeat annotation info, but provides behavioral context beyond it.

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?

The description is structured with sections, bullet points, and code examples, making it easy to scan. While somewhat lengthy due to the many target options, every sentence earns its place. Could be slightly more concise, but the structure aids comprehension.

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 the tool has only 2 parameters (both optional), an output schema exists (so return values are covered), and no nested objects, the description is fully complete. It covers all possible parameter values, usage patterns, and links to sibling tool ha_get_integration for finding entry_id.

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

Parameters5/5

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

The input schema has no descriptions (0% coverage), but the description compensates fully by enumerating all 17 valid target options with explanations, and thoroughly explains entry_id usage including how to find the id and that combining with target is a validation error. This adds critical meaning beyond the schema.

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?

The description explicitly states the tool reloads Home Assistant configuration without a full restart, using a specific verb ('reload') and resource ('core components'). It distinguishes from sibling ha_restart by emphasizing speed and avoiding full restart. The extensive target list further clarifies scope.

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?

The description includes a dedicated 'When to Use' section listing specific scenarios (e.g., after editing automation YAML, modifying customize.yaml). It also explains entry_id usage and warns against combining it with an explicit target, providing clear guidance on proper invocation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/homeassistant-ai/ha-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server