Skip to main content
Glama

Get HA status

proxmox_get_ha_status
Read-only

Retrieve Proxmox VE high-availability status to check cluster quorum, CRM master, node LRM states, fencing/arming, and HA-managed services with their nodes and states.

Instructions

High-availability overview: quorum, the current CRM master, each node's LRM state (active/idle/maintenance, last update), fencing/arming state (PVE 9.1+), and every HA-managed service with its node and state. Use proxmox_list_ha_resources for the configured settings.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.3/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 useful behavior beyond that: the scope of the returned snapshot (runtime vs. configuration) and a version-gating caveat that fencing/arming state only appears on PVE 9.1+. It does not mention response size or whether the payload is a flat aggregate, which matters given idempotentHint=false.

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, zero filler: the first front-loads the returned content in a scannable list, and the second immediately handles the sibling routing. Nothing is redundant with the title or annotations.

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?

With no output schema, the description carries the burden of explaining return values and does so thoroughly by enumerating the fields an agent will receive. For a single-optional-parameter read tool with annotations covering safety, no information needed to call it correctly is missing.

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?

There is a single optional parameter with 100% schema description coverage, so the schema already explains that raw returns full unprocessed API objects. The description adds nothing about the parameter or how the response shape changes when it is set, so the baseline of 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?

The description names the specific resource (HA status overview) and enumerates exactly what it contains: quorum, CRM master, per-node LRM state with last update, fencing/arming state, and every HA-managed service with node and state. It also explicitly distinguishes itself from proxmox_list_ha_resources, which returns configured settings rather than runtime state.

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 one clear routing rule: use proxmox_list_ha_resources for configured settings, implying this tool is for live/runtime state. That is a genuine alternative-with-condition, but there is no explicit statement of when this tool should be preferred over other status tools such as proxmox_get_cluster_status or proxmox_get_node_status.

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