Unofficial-Proxmox-MCP

pve_get_node_status

Retrieve detailed Proxmox node telemetry, including PVE and kernel versions, CPU topology, load averages, and memory/swap usage in MB, to assess node health and capacity.

Instructions

Get deep telemetry for a Proxmox node: PVE version, kernel version, CPU sockets/cores/model, load averages, and memory/swap utilization in MB.

Args: node: Target node name (e.g. 'pve'). Defaults to cluster default node if empty.

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

Input Schema

Name	Required	Description	Default
`node`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does meaningful work: the 'Get' verb makes the read-only nature clear, the returned data set is spelled out, and the fallback behavior when node is empty ('Defaults to cluster default node') is disclosed. It does not cover failure behavior for an invalid node name or any permission requirements, which keeps it below a 5.

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 purpose and returned fields, then a compact Args block. Slightly redundant to enumerate return fields when an output schema exists, but the enumeration is short and aids tool selection.

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?

A single optional parameter, an output schema covering return values, and a description that names the data returned and the default-node fallback – enough for an agent to invoke it correctly. Only auth/error context is missing.

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?

Schema description coverage is 0%, so the description must compensate, and it does: the single parameter is described as a target node name, given a concrete example ('pve'), and its default-when-empty semantics are explained. That is the key meaning an agent needs beyond the bare string type.

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 specific verb ('Get deep telemetry') and resource ('a Proxmox node'), then enumerates exactly what is returned (PVE version, kernel, CPU topology, load averages, memory/swap in MB). An agent can tell this apart from pve_list_nodes (enumeration) or pve_get_system, though it never names an alternative explicitly.

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?

Usage is only implied: 'deep telemetry for a node' suggests using it when node-level health/metrics are needed. There is no explicit when-to-use, when-not-to-use, or pointer to a sibling such as pve_get_system, leaving the agent to infer the boundary.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.