Skip to main content
Glama

List HA groups

proxmox_list_ha_groups
Read-only

List Proxmox HA groups with node priorities and restrictions. Use it to inspect legacy cluster HA group configuration before migrating to node-affinity rules.

Instructions

List HA groups (node lists with priorities, restricted, nofailback). Deprecated in PVE 9, where groups are migrated to node-affinity rules (proxmox_list_ha_rules).

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

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds non-obvious lifecycle context (deprecated in PVE 9) that annotations cannot express. It also sketches what each group record contains, which helps the agent interpret results. It omits pagination/result-size behavior, but that is a minor gap for a read-only list tool.

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?

Two sentences, no filler, with the resource definition front-loaded and the migration warning second. Every clause carries information the agent can act on.

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

Completeness4/5

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

For a two-optional-parameter, read-only list tool with no output schema, the description covers purpose, result shape, and the deprecation/migration path. The only meaningful omission is the meaning of the `search` and `fields` parameters, which the 0%-coverage schema leaves entirely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and both parameters (fields, search) are undocumented in the schema. The description says nothing about either one, so an agent gets no signal on what `search` matches or how `fields` projects the result. The field list in parentheses describes group record contents, not the input parameters, so it does not compensate.

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?

The description states a specific verb and resource ("List HA groups") and immediately characterizes the returned content ("node lists with priorities, restricted, nofailback"). The deprecation note naming proxmox_list_ha_rules as the successor distinguishes it from the nearest sibling without the agent needing to open any schema.

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

Usage Guidelines4/5

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

It gives explicit routing guidance: deprecated in PVE 9, groups migrated to node-affinity rules, use proxmox_list_ha_rules instead. That is real when-to-use/when-to-prefer-an-alternative context. It stops short of saying when this tool is still the right choice (e.g., pre-PVE 9 clusters) or how it differs from proxmox_get_ha_group for a single group.

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