Skip to main content
Glama
Fistacho

ha-nexus-agent

by Fistacho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List HACS repositories

hacs_list_hacs_repositories
Read-onlyIdempotent

Browse and check the state of HACS repositories already known to your Home Assistant instance, optionally filtered by category.

Instructions

List HACS repositories known to this Home Assistant instance.

Calls the hacs/repositories/list WebSocket command, optionally scoped to one category.

Use when: browsing or checking the state of repositories HACS already knows about (installed or not). Not for: repositories not yet added to HACS at all — use hacs_add_custom_repository first. Returns: list of HACS repository dicts as reported by HACS, or {"error": ..., "hint": ...} if the WebSocket call fails. Errors: {"error": str(exception), "hint": "HACS may not be installed, or the WS command name has changed"} when the WebSocket command fails, e.g. because HACS is not installed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter to one HACS category: integration, plugin, theme, template, appdaemon or python_script. Omit to list every category.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.25.1
    • addedInput schema / properties / category / description
      Added value: +"Filter to one HACS category: integration, plugin, theme, template, appdaemon or python_script. Omit to list every category."
  2. First observedv0.3.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint/openWorldHint, so safety is covered. The description adds real context beyond that: the WS command invoked, that results are as-reported-by-HACS, and the specific error payload plus hint when HACS is missing or the command name changed.

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?

Front-loaded with purpose and structured with Use when / Not for / Returns / Errors labels, which is easy to scan. Slightly verbose — the error payload is described twice (in Returns and again in Errors).

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?

For a one-parameter read-only list tool with full schema coverage, annotations, and an output schema, the description covers purpose, routing, and failure modes. An agent has everything needed to select and invoke it correctly.

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% and the single `category` parameter is fully documented in the schema with its enum-like values and the omit-to-list-all behavior. The description's 'optionally scoped to one `category`' restates rather than extends the schema, so baseline 3 applies.

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 HACS repositories known to this Home Assistant instance') and names the underlying operation (`hacs/repositories/list`), which cleanly separates it from siblings like hacs_get_hacs_repository and hacs_add_custom_repository.

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 explicit 'Use when' (browsing/checking state of repositories HACS already knows about) and 'Not for' guidance pointing at the alternative `hacs_add_custom_repository` for repos not yet in HACS. 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