Skip to main content
Glama

Get node system report

proxmox_get_node_report
Read-only

Generate a node's pvereport: a long text dump of versions, hardware, storage, network, cluster and guest configuration for support requests. Truncates to max_chars.

Instructions

The node's pvereport: a long text dump of versions, hardware, storage, network, cluster and guest configuration, as used for support requests. Large; truncated to max_chars. Can take a while to generate.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
max_charsNoTruncate the text to this many characters (default 50000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly and closed-world, but the description adds genuinely new facts: the payload is large, output is truncated at max_chars rather than failing, and generation is slow. It does not say what truncation looks like in the response or whether sections are cut mid-way, which would have pushed this higher.

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?

Three short sentences, front-loaded with what the tool returns, followed by the size/truncation caveat and the latency warning. No filler and no restatement of the title.

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 correctly takes on the burden of describing the return value as a long text dump and flags truncation and latency. The only gap is not describing the shape of the returned text or how an agent can tell the output was cut off.

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?

Schema coverage is 100%, so node and max_chars are already documented, including the default and the proxmox_list_nodes pointer. The description only reinforces that max_chars truncates (rather than paginates or errors), which is a marginal addition over the schema's own wording.

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 underlying artifact (pvereport) and enumerates its contents — versions, hardware, storage, network, cluster, guest configuration — which distinguishes it from the narrow single-domain siblings like proxmox_get_node_stats or proxmox_get_node_status. An agent can tell this is the aggregate diagnostic dump rather than a focused query.

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?

The phrase 'as used for support requests' implies a diagnostic/bundling use case, and 'Large; truncated to max_chars' plus 'Can take a while' hints at when it is expensive to call. However, it never says 'use a narrower sibling when you only need X,' so the alternative choice is left to inference.

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