ha-nexus-agent

Overview Schema Source Related Servers Discussions Admin

List all config entries

system_list_integrations

Read-onlyIdempotent

Retrieve every Home Assistant config entry in any state with all raw fields. Use for unfiltered config-entry data, not compact listings.

Instructions

List every Home Assistant config entry, whatever its state.

Calls the raw config_entries/get WebSocket command and returns it unfiltered: every field HA stores per entry, in any state (loaded, not_loaded, setup_error, disabled). On instances with many integrations this can be a large payload.

Use when: the raw config-entry objects, with every field, are needed. Not for: a compact, easier-to-scan listing — use system_get_all_integrations, which strips this down to entry_id/domain/title/state/source. Returns: list of raw config-entry dicts as returned by HA's WebSocket API. Errors: raises RuntimeError if the underlying WebSocket call fails (e.g. auth or WS-level error). Limits: no pagination or filtering; large HA instances get a large response.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0May 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Beyond the annotations (which already declare readOnly/idempotent/non-destructive), the description adds meaningful behavior: it discloses that output is unfiltered, that the response can be large on busy instances, that there is no pagination or filtering, and that a RuntimeError is raised on WS failure.

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?

Front-loads what it does, then uses labeled sections (Use when / Not for / Returns / Errors / Limits) that are easy to scan. Every sentence carries information an agent needs.

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?

Despite a zero-param schema and an existing output schema, the description covers return shape, failure mode, and the large-payload caveat. An agent has everything needed to select and call it correctly.

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?

The tool takes zero parameters, so the schema baseline is 4. The description correctly conveys there is nothing to configure (no filtering or pagination), matching the empty input schema.

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 ('List every Home Assistant config entry') and explicitly scopes it to raw, unfiltered output. It distinguishes itself from the sibling system_get_all_integrations by name and by what each returns.

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?

Provides an explicit 'Use when' clause (raw config-entry objects with every field) and a 'Not for' clause that names the alternative tool and the reason to pick it. 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