Skip to main content
Glama
TheWhykiki

hass-mcp

by TheWhykiki

ha_list_entity_registry

List all entity registry entries from Home Assistant to view configured entities and their unique identifiers.

Instructions

List Home Assistant entity registry entries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for 'ha_list_entity_registry'. It calls ha.listEntityRegistry() and returns the JSON result.
    server.tool(
      'ha_list_entity_registry',
      'List Home Assistant entity registry entries.',
      ListEntityRegistryInput.shape,
      async () => {
        const entities = await ha.listEntityRegistry()
        return {
          content: [{ type: 'text', text: JSON.stringify(entities, null, 2) }],
        }
      },
    )
  • The listEntityRegistry() method on HomeAssistantClient that makes a WebSocket call to 'config/entity_registry/list'.
    async listEntityRegistry(): Promise<EntityRegistryEntry[]> {
      return await this.wsCall('config/entity_registry/list')
    }
  • The wsCall private helper that sends a WebSocket message (used by listEntityRegistry).
    private async wsCall<T>(type: string, payload: Record<string, unknown> = {}): Promise<T> {
      const connection: any = await this.ensureConnected()
      if (typeof connection.sendMessagePromise !== 'function')
        throw new Error('Home Assistant connection does not support sendMessagePromise')
    
      return await connection.sendMessagePromise({ type, ...payload }) as T
    }
  • The Zod schema definition for ListEntityRegistryInput (empty object, no parameters).
    export const ListEntityRegistryInput = z.object({}).strict()
  • src/index.ts:121-131 (registration)
    The tool is registered via server.tool() with name 'ha_list_entity_registry'.
    server.tool(
      'ha_list_entity_registry',
      'List Home Assistant entity registry entries.',
      ListEntityRegistryInput.shape,
      async () => {
        const entities = await ha.listEntityRegistry()
        return {
          content: [{ type: 'text', text: JSON.stringify(entities, null, 2) }],
        }
      },
    )
Behavior2/5

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

No annotations exist, and the description only says 'List' without confirming read-only behavior, permissions, or side effects. Minimal disclosure.

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?

Single sentence, concise, and front-loaded. Lacks structure but appropriate for a simple list operation.

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?

No output schema, no annotations, and minimal description. Agent lacks context about return format or scope of entries.

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

Parameters4/5

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

Input schema has 0 parameters (100% coverage). Baseline 4 applies; description adds no param info but is not required.

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

Purpose5/5

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

The description clearly states 'List Home Assistant entity registry entries', using a specific verb and resource. It distinguishes from sibling tools like ha_list_areas and ha_list_devices.

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 tool vs alternatives (e.g., ha_list_states, ha_list_services). No exclusions or context provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TheWhykiki/hass-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server