Skip to main content
Glama
Sign In
hass-mcp-server

hass-mcp-server

by jarahkon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ha_get_entity

Fetch the full state and attributes of a specific Home Assistant entity by its entity ID.

Instructions

Get the full state and attributes of a specific entity

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": "ha_get_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
entity_idYesEntity ID (e.g. 'light.living_room', 'sensor.temperature')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.10

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, and description only states 'get' without disclosing any behavioral traits (e.g., read-only, caching, rate limits). The tool is simple but transparency is minimal beyond the inferred read operation.

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?

Single sentence that is front-loaded and contains no extraneous words. Every word is necessary and earns its place.

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?

Given low complexity (1 param, no nested objects), the description hints at return value ('full state and attributes'), which is sufficient for inference. However, no output schema or explicit return format may leave room for ambiguity.

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 has 100% coverage with description for entity_id. Description adds no extra semantics beyond the schema, meeting the baseline for high schema coverage.

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?

Description clearly states 'Get the full state and attributes of a specific entity', specifying the action (get), resource (entity), and scope (full state/attributes). It distinguishes from sibling tools like ha_get_states which likely returns all entities.

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 versus alternatives. Does not mention context such as prerequisites, or compare with similar tools like ha_get_states.

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