Retrieve all Home Assistant automations with their entity IDs, slugs, names, states, and last trigger timestamps for monitoring and management.
List every automation known to Home Assistant.
Returns the entity_id, slug id, friendly name, current state, and last trigger timestamp for each automation (as reported by the state machine).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully describes the returned fields (entity_id, slug, name, state, last trigger), but omits read-only declaration, pagination/volume behavior, permissions, and whether disabled or unregistered automations are included.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two front-loaded sentences with zero filler; the scope statement comes first and the return payload second, each earning its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-param list tool with no output schema, the description compensates by enumerating the returned fields, which is genuinely useful. Minor gaps remain around scope nuances (disabled automations) and read-only nature, but nothing blocking.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, which is the baseline-4 case. There is nothing for the description to disambiguate, and it correctly does not invent filtering options that do not exist.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('List every automation'), so the operation is unambiguous. It does not explicitly contrast itself with siblings like get_automation or list_entities, but 'every' vs 'get' implies the distinction.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by the name and the 'every automation' scope, but there is no explicit when-to-use guidance, no mention of when to prefer get_automation for a single item, and no exclusions. Adequate but leaves routing to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.