Skip to main content
Glama

Get cluster overview

proxmox_get_cluster_status
Read-only

Retrieve a one-call overview of a Proxmox VE cluster, including quorum, node health, guest counts, storage usage, and HA state to assess cluster status quickly.

Instructions

One-call overview of the whole cluster: name, quorum, Proxmox version, every node (online state, CPU, memory, uptime), guest counts by state, totals, storage usage and HA state. A good first call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/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 that everything comes back in a single aggregate call, implying no pagination or per-node fan-out. It does not describe response size, latency on large clusters, or failure behavior when quorum is lost. Useful but modest beyond the annotations.

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, front-loaded with the scope claim, then the field list, then the usage tip. The enumeration is dense but every item is returned data, so nothing is wasted.

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?

With no output schema, the description carries the burden of describing returns, and it does so thoroughly (nodes, guest counts, totals, storage, HA). For a zero-parameter read tool with full annotation coverage this is close to complete; only response shape or failure semantics are unstated.

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?

Zero parameters, so there is nothing to disambiguate and the schema is trivially complete. The description correctly implies no filtering or scoping arguments exist.

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?

States a concrete verb+resource ('One-call overview of the whole cluster') and enumerates the returned content (quorum, version, node state, guest counts, storage, HA). That is clearly distinct from config-oriented siblings such as proxmox_get_cluster_config, though it never explicitly names an alternative. Clear enough that an agent knows what it gets, short of explicit sibling differentiation.

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

Usage Guidelines3/5

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

'A good first call' is a real usage hint that positions the tool as an orientation step. It does not say when to prefer proxmox_get_node_status or proxmox_get_capacity_report instead, nor any exclusions, so usage is implied rather than prescribed.

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