Skip to main content
Glama

List nodes

proxmox_list_nodes
Read-only

List Proxmox VE cluster nodes with online status, CPU and memory usage, uptime, and subscription level to monitor node health and capacity.

Instructions

List the cluster's nodes with online state, CPU and memory usage, uptime and subscription level.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already establish this as a read-only, non-open-world operation, so the safety profile is covered. The description does add value by disclosing the returned attributes (state, CPU, memory, uptime, subscription), but it says nothing about response shape, size, or why idempotentHint is false for what appears to be a read.

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?

A single front-loaded sentence with the resource first and the returned data enumerated after. No filler, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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's enumeration of returned fields usefully describes what comes back, and annotations cover the read-only nature. However, for a tool with 3 optional parameters, leaving `search` and `fields` entirely unexplained is a real gap an agent would hit on first use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Only 33% schema description coverage exists, and only `raw` is documented in the schema; `fields` and `search` carry no description anywhere. The description does not compensate at all — it never mentions filtering by search term, selecting fields, or the tradeoff of raw output.

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?

"List the cluster's nodes" gives a specific verb and a specific resource, and the enumerated payload (online state, CPU, memory, uptime, subscription) makes the scope unambiguous versus other list tools such as proxmox_list_containers or proxmox_list_guests. It stops short of explicitly naming a sibling to contrast with, so it lands at 4 rather than 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite (e.g. cluster membership/auth), and no mention of alternatives such as listing guests or containers. The agent must infer from the resource name alone that this is the entry point for node-level inventory.

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