Skip to main content
Glama
Sign In
Home Assistant MCP Server

Home Assistant MCP Server

by rilhia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get automation config

get_automation
Read-onlyIdempotent

Retrieve a Home Assistant automation's full stored configuration, current entity state, and any high-risk actions by supplying its config ID or entity ID.

Instructions

Read the full stored configuration of one automation through the Home Assistant config pipeline, together with its entity state and any high risk actions it contains. Accepts the config id or the entity id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "automation_id": "<automation_id>"
    },
    "name": "get_automation"
  }
}

Input Schema

NameRequiredDescriptionDefault
automation_idYesThe automation config id or its entity id, for example 'automation.example'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds genuine value by disclosing that the response includes the config pipeline data, live entity state, and any high-risk actions detected inside the automation, which is not derivable from annotations.

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

Conciseness5/5

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

Two sentences with no filler. The primary behavior is front-loaded and the accepted identifier forms come last, matching the order an agent needs them.

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?

There is no output schema, so the description carries the burden of describing return content, and it does so at a useful level: config, entity state, and high-risk actions. What remains thin is failure behavior for an invalid or missing id, which the description does not address.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter already documents that it accepts either the config id or the entity id. The description restates this same fact without adding format, resolution, or ambiguity-handling guidance, so the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reading the full stored configuration of a single automation, plus its entity state and high-risk actions. The singular scope distinguishes it implicitly from list_automations, but no sibling is named, so the differentiation is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: the description suggests you call this when you need one automation's stored config. It never contrasts with get_automation_trace, validate_automation_config, or list_automations, so an agent must work out when this is the right tool for a given question.

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