Connects Claude to a Home Assistant instance via the REST API
Server has 10 tools with complete input schemas and descriptions. Naming follows verb_noun convention (get_, turn_, set_, call_, trigger_). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Parameters are typed and constrained (e.g., hours 1 - 168). However, output schemas are not documented, LLMs cannot predict response structure. Error handling is present but generic ('Unexpected error'). No tool annotations (readOnlyHint/destructiveHint). Security is good (token via env var, no secrets in params). Composition is sound, tools are single-purpose and chainable.
Call a Home Assistant service with optional entity targeting and service data
Get the current state and attributes of a single entity
Get historical state changes for an entity
Get the current state of all entities, optionally filtered by domain
Render a Jinja2 template using Home Assistant's template engine
Set the target temperature for a climate entity
Toggle an entity on or off
Output schemas not documented. LLMs cannot predict response structure, forcing them to guess what fields are returned and how to chain tools.
Tool annotations missing. No readOnlyHint on read tools (get_*, get_history, render_template) or destructiveHint on write tools (turn_*, toggle, trigger_automation). LLMs cannot distinguish safe from risky operations.
Descriptions are generic and under 100 chars. E.g., 'Turn on an entity with optional service data' lacks context on when to use vs turn_off/toggle, what service_data does, or what the response contains.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Trigger an automation by its entity ID
Turn off an entity
Turn on an entity with optional service data
Error messages are generic. '_handle_error' returns 'Unexpected error: <type>: <msg>' without recovery guidance. LLMs cannot self-correct or know whether to retry.
call_service is overly generic. It accepts any domain/service/entity_id, making it a catch-all that duplicates turn_on, turn_off, toggle, and set_climate_temperature. LLMs will struggle to choose between them.