Retrieve a single Home Assistant automation by ID to inspect its live state and attributes. Fetch raw YAML triggers, conditions, and actions with the YAML variant.
Get a single automation by id (e.g. 'solaredge_power_notify').
Returns live state + attributes. Use get_automation_yaml for the raw
YAML config (triggers / conditions / actions).
| Name | Required | Description | Default |
|---|---|---|---|
| automation_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations are absent, so the description carries the full burden. It adds some behavioral context by stating that it returns live state and attributes, which is useful beyond the schema, but doesn't mention if the operation is read-only, error behavior for invalid ids, or authentication requirements.
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 short sentences, front-loaded with the primary purpose, followed by the return value and a clear pointer to the alternative tool for YAML. No unnecessary words.
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 simple single-entity getter with one parameter, the description covers purpose, return value, and distinguishes from the YAML alternative. It lacks annotation-level behavioral details, but given the tool's simplicity and lack of output schema, it is nearly complete.
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?
Schema coverage is 0%, so descriptive parameter info would be valuable. The description provides an example id format ('solaredge_power_notify') but only for the singular 'automation_id' parameter, adding marginal value over the bare schema. It doesn't describe the id format fully or where to obtain it.
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 ('Get a single automation by id') and includes a concrete example id. It explicitly distinguishes itself from the sibling get_automation_yaml by clarifying what data it returns versus the raw YAML.
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?
Clear context: use this tool to get a single automation and its live state, and use get_automation_yaml for the raw config. However, it doesn't mention list_automations as the alternative for getting multiple automations, and provides no exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.