Skip to main content
Glama
Sign In
Home Assistant MCP Server

Home Assistant MCP Server

by rilhia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get area summary

get_area_summary
Read-onlyIdempotent

Retrieve all devices and entities assigned to a Home Assistant area by name or ID, grouped by device with current states, to inspect what a room contains and how it is configured.

Instructions

All devices and entities assigned to a physical area, grouped by device, with current states. Accepts the area name or 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": {
      "area_name": "<area_name>"
    },
    "name": "get_area_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
area_nameYesArea name or id, for example 'Living Room' or 'living_room'.
max_entitiesNoCap on entities listed.
include_disabledNoInclude disabled registry entries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

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 covered. The description usefully adds what content comes back (devices grouped with entity states), but says nothing about truncation behavior when max_entities is hit or what happens for an unknown area.

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 tight sentences with zero filler; the returned content leads and the identifier detail follows. Nothing is redundant and nothing could be removed without losing information.

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 carries the burden of describing the return shape and does so adequately: devices and entities grouped by device with current states. Remaining gaps – truncation signaling and not-found behavior – are minor for a read-only summary tool.

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 description coverage is 100%, so every parameter is already documented including defaults, bounds, and the name-or-id example. The description's 'Accepts the area name or id' simply restates the schema, adding no new semantics.

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?

The description names a specific resource and scope: all devices and entities in a physical area, grouped by device, with current states, plus accepted identifier forms. It is clearly distinct from list_areas (which enumerates areas rather than summarizing one), though it never names that sibling to make the boundary explicit.

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 by the phrase 'assigned to a physical area' – an agent can infer this is for inspecting a single area, but there is no statement of when to prefer this over list_areas, get_entity_details, or get_dashboard, and no note on how to obtain a valid area name.

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