Skip to main content
Glama
homeassistant-ai

Home Assistant MCP Server

Official
by homeassistant-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Label

ha_config_get_label
Read-onlyIdempotent

Retrieve Home Assistant label configurations: list all labels or fetch a specific one by ID. Use this to inspect label details before assigning them to entities, devices, or areas.

Instructions

Get label info - list all labels or get a specific one by ID.

Without a label_id: Lists all Home Assistant labels with their configurations. With a label_id: Returns configuration for that specific label.

EXAMPLES:

  • List all labels: ha_config_get_label()

  • Get specific label: ha_config_get_label("my_label_id")

Use ha_config_set_label() to create or update labels. Use ha_set_entity(labels=["label1", "label2"]) to assign labels to entities, ha_set_device(labels=[...]) for devices, or ha_set_area_or_floor(kind="area", labels=[...]) for areas.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
label_idNoID of the label to retrieve.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv8.6.0
    • changedInput schema / properties / label_id / description
      Previous value: -"ID of the label to retrieve. If omitted, lists all labels."New value: +"ID of the label to retrieve."
  2. First observedv7.14.2

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: the dual-mode list-vs-get semantics driven by parameter presence, which the annotations do not convey.

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?

Behavioral core is front-loaded, then examples, then cross-references. Every sentence serves a purpose, though the EXAMPLES block and cross-reference list make it longer than strictly minimal.

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

Completeness5/5

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

An output schema exists, so return values need no explanation here. For a single-parameter, fully documented read tool, the description covers mode selection, examples, and related sibling routing, leaving no gap an agent needs to fill.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema's terse 'ID of the label to retrieve' by explaining the consequence of omitting it (returns all labels with configurations) versus supplying it (returns that label's config). It also supplies concrete example calls.

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?

States a specific verb and resource ('Get label info') and explicitly distinguishes the two modes: listing all labels vs. retrieving one by ID. An agent can tell it apart from ha_config_set_label and the assignment tools without opening a schema.

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

Usage Guidelines5/5

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

Names the exact condition selecting each mode ('Without a label_id' vs 'With a label_id') and routes the agent to the correct alternatives: ha_config_set_label for create/update, and ha_set_entity/ha_set_device/ha_set_area_or_floor for assignment. Nothing is left to inference.

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