Skip to main content
Glama

List HA resources

proxmox_list_ha_resources
Read-only

List HA-managed VMs and containers with requested state, HA group, restart and relocate limits, failback, comment, guest name, and current node and CRM status.

Instructions

List HA-managed VMs and containers with their requested state, group, restart/relocate limits, failback, comment, guest name and current status (node and CRM state).

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_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly VMs or only containers
limitNoMaximum number of results (default 500)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value by specifying the returned fields, including node and CRM state, and the 'current status' wording signals live/observed data rather than cached config. It omits pagination behavior despite a default limit of 500, which matters for a 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with the verb and scope front-loaded, followed by a compact list of returned attributes. No filler, though the long run-on field enumeration would read better as a short structured list.

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?

Without an output schema, describing return fields is the right call and is done reasonably. However, for a paginated list tool with four parameters and one undocumented field, the description leaves result-size limits and filtering options entirely to the schema.

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?

The description says nothing about the type, limit, fields, or search parameters, so it adds no meaning beyond the schema. Schema coverage is 75%, leaving the undescribed 'fields' array to be inferred purely from its name. With this coverage gap, the description should have compensated and does not.

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 (List) and a precisely scoped resource set (HA-managed VMs and containers), which distinguishes it from the generic proxmox_list_resources. It also enumerates the returned attributes, so an agent can tell what data it gets. It stops short of naming the sibling for non-HA inventory explicitly.

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?

Usage is only implied by the 'HA-managed' qualifier; there is no explicit statement of when to choose this over proxmox_list_resources or proxmox_get_ha_resource for a single entry. No prerequisites, exclusions, or alternative routing guidance are given.

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