Skip to main content
Glama
Sign In
Home Assistant MCP Server

Home Assistant MCP Server

by rilhia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List integrations (config entries)

list_integrations
Read-onlyIdempotent

Lists configured Home Assistant integrations and helpers with entry IDs, domains, titles, states, and problem reasons; filter to problems_only to find entries that failed to load or need attention.

Instructions

List configured integrations and helpers with their entry_id, domain, title, state and any problem reason. Set problems_only to see just entries that failed to load or need attention.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoText matched against title and domain.
domainNoOnly this integration domain, for example 'mqtt'.
max_itemsNo
problems_onlyNoOnly entries in a state other than loaded. Entries you chose to ignore are skipped.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.2/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 adds the shape of the result (entry_id, domain, title, state, problem reason), but says nothing about truncation when more entries exist than max_items, or about ordering.

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?

Two sentences, front-loaded with what is returned, no filler. The second sentence is purely a parameter hint, which is acceptable but slightly redundant with the schema on problems_only.

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

Completeness3/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 correctly lists the returned fields, which is the main gap it needed to close. It is still silent on result-limit behavior, ordering, and how this differs from the other listing tools in the sibling set.

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 coverage is 75%, with query, domain and problems_only described inline; only max_items lacks a schema description, and the description does not fill that gap. The one parameter it does explain (problems_only) largely restates the schema text, so value added over the structured fields is marginal.

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 gives a specific verb and resource ('List configured integrations and helpers') and enumerates the returned fields, so the agent knows what it is getting. It does not, however, distinguish itself from near neighbors such as list_helpers, list_repairs, or find_problems, which overlap in domain.

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?

The only hint is 'Set problems_only to see just entries that failed to load', which is parameter guidance rather than tool-selection guidance. There is no statement of when to prefer this over find_problems or list_helpers, nor any prerequisite or exclusion.

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