Home Assistant MCP Server

Overview Schema Source Related Servers Discussions Admin

Get entity details

get_entity_details

Read-onlyIdempotent

Retrieve complete details for a single Home Assistant entity: current state, attributes, decoded features, registry info, and domain services. Use it to inspect or troubleshoot one entity.

Instructions

Complete inspection of one entity: current state, all attributes, decoded supported features, registry data (platform, device, area, disabled or hidden status) and the services available for its domain.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_entity_details"
  }
}

Input Schema

Name	Required	Description	Default
`entity_id`	Yes	Full entity id, for example 'light.kitchen'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds value by disclosing the breadth of returned data (decoded features, registry metadata), but says nothing about behavior when the entity_id does not exist or about response size.

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?

One front-loaded sentence that leads with the scope ('Complete inspection of one entity') and then enumerates the payload with no filler or redundancy.

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?

With no output schema, the description must carry the return-value burden, and it does so by enumerating the fields returned. Only the error/not-found case and any size caveats are missing for a tool of this simplicity.

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?

There is a single parameter with 100% schema description coverage, including a concrete example ('light.kitchen'), so the baseline is 3. The description adds no further semantics about the identifier's format or resolution beyond what the schema already states.

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 ('Complete inspection of one entity') and enumerates exactly what is returned: current state, attributes, decoded supported features, registry data (platform, device, area, disabled/hidden status) and available services. That is far beyond a restatement of the name, though it does not distinguish itself from siblings like search_entities or find_related.

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 word 'one entity' signals a single-entity lookup rather than the multi-entity search_entities sibling, but there is no explicit when-to-use or when-not-to-use statement and no alternatives named.

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