Skip to main content
Glama

Get node status

proxmox_get_node_status
Read-only

Retrieve detailed hardware and system status for a Proxmox VE node, including CPU usage, memory, swap, root filesystem, kernel, version, boot mode, uptime and subscription state.

Instructions

Detailed status of one node: CPU model/sockets/cores and usage, IO wait, load average, memory/swap/root filesystem usage, kernel, Proxmox VE version, boot mode (EFI/BIOS, secure boot), uptime, KSM sharing and the subscription status. Use proxmox_list_nodes for all nodes at a glance and proxmox_get_node_stats for history.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/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 the safety profile is carried by structured data. The description adds real value by disclosing the breadth of returned fields (including subscription status, which overlaps a dedicated sibling), but says nothing about response size, the cost of raw=true, or error behavior for an unknown node. Note idempotentHint=false on a read-only status call is unusual but the description neither confirms nor contradicts it.

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 purpose, then a dense field enumeration, then a routing sentence — no wasted framing. The field list is long but earns its place because overlapping siblings (subscription, stats) exist and the list establishes coverage boundaries.

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 only two optional parameters and no output schema, the field enumeration effectively substitutes for return-value documentation, which is the right call. It stops short of describing response shape or how raw changes it, a minor gap for a low-complexity read tool.

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% and both parameters are documented in-schema, including the PROXMOX_DEFAULT_NODE fallback and a forward reference to proxmox_list_nodes. The description adds no extra meaning about node naming or what the raw flag changes beyond what the schema states, so the baseline 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 opens with a specific verb+resource ("Detailed status of one node") and then enumerates the exact data covered: CPU model/sockets/cores and usage, IO wait, load average, memory/swap/rootfs, kernel, PVE version, boot mode, uptime, KSM sharing, subscription status. That enumeration lets an agent distinguish this from proxmox_get_node_stats and proxmox_get_node_subscription without opening either schema.

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

Usage Guidelines5/5

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

It explicitly routes the agent: proxmox_list_nodes for all nodes at a glance, proxmox_get_node_stats for history. Both the selection condition and the alternatives are named, so an agent knows this tool is the point-in-time, single-node option.

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