Skip to main content
Glama
Sign In
ha-automation-mcp

ha-automation-mcp

by aderik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_registry_entity

Retrieve full Home Assistant entity registry details for a given entity_id to inspect metadata, area, device, and configuration without manual YAML edits.

Instructions

Get full registry details for a single 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": {
      "entity_id": "<entity_id>"
    },
    "name": "get_registry_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full behavioral burden. 'Get' implies a safe read, but nothing is said about permission requirements, error behavior for an unknown entity_id, or what 'full registry details' actually includes.

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

Conciseness4/5

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

A single short sentence, front-loaded with the verb and resource, with no wasted words. Brevity here reflects terseness rather than padding, though it borders on under-specification.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and 0% parameter coverage, the description should at minimum sketch what registry fields are returned and how the id is sourced. It leaves both gaps open for a tool whose only job is to return that data.

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

Parameters2/5

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

Schema description coverage is 0% for the single entity_id parameter, so the description must compensate and does not — it never explains the expected id format or where an agent obtains a valid one. It only restates that the id identifies one entity.

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 (Get), resource (registry entity), and scope (full details for a single entity_id). The word 'single' implicitly contrasts with the sibling list_registry_entities, but no sibling is named explicitly, so the differentiation is only implied.

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

Usage Guidelines2/5

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

No guidance on when to use this versus list_registry_entities, get_device, or update_registry_entity. The agent must infer that this is the fetch-one-by-id counterpart to the list tool.

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