Skip to main content
Glama

List HACS pending upgrades

hacs_list_hacs_critical_updates
Read-onlyIdempotent

Identify installed HACS and Marketplace repositories with pending upgrades so you can update them without filtering the full repository list.

Instructions

List installed HACS / Marketplace repositories that have a pending upgrade available.

Calls the same list command as hacs_list_hacs_repositories (marketplace/repositories/list on HA 2026.11+, hacs/repositories/list on older HA) and keeps entries whose pending_upgrade flag is set, despite this tool's name — there is no separate "critical" severity here.

Use when: finding what needs hacs_update_hacs_repository without filtering the full list manually. Not for: every repository regardless of upgrade state — use hacs_list_hacs_repositories. Returns: list of repository dicts with pending_upgrade truthy, or an error dict. Errors: {"error", "code", "backend", "hint"} when the command fails; {"error": "Unexpected response shape", "raw": result} when it does not return a list.

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": "hacs_list_hacs_critical_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description spends its budget on things annotations cannot express: the underlying command (`marketplace/repositories/list` on HA 2026.11+, `hacs/repositories/list` on older HA), the client-side `pending_upgrade` filtering, and two distinct error shapes including an 'Unexpected response shape' fallback with a `raw` payload. That is genuinely useful operational context beyond the safety profile.

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 the one-line purpose, then clearly labeled Use when / Not for / Returns / Errors blocks, which is easy to scan. The multi-line HA-version detail on the backend command is slightly verbose but earns its place as version-compatibility information rather than noise.

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-arg, low-complexity tool, the description covers selection semantics, filtering behavior, backend command and version variation, plus return and error shapes. Even though an output schema exists, the error-variant disclosure adds information an agent needs to handle failure paths.

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 baseline applies; there is nothing for the description to disambiguate. It correctly avoids padding with irrelevant argument talk.

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 (list) and resource (installed HACS/Marketplace repositories with a pending upgrade) and immediately disentangles the misleading 'critical' in its own name, noting there is no separate critical severity. It also names the sibling `hacs_list_hacs_repositories` as the unfiltered variant, so an agent can pick between the two without opening either 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?

Explicit 'Use when:' clause ties it to finding what needs `hacs_update_hacs_repository` without manual filtering, and an explicit 'Not for:' clause routes to `hacs_list_hacs_repositories` when all repositories are wanted. Both the positive trigger and the alternative are named.

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