Skip to main content
Glama

List cluster resources

proxmox_list_resources
Read-only

Lists Proxmox cluster resources such as nodes, VMs, storage, pools, and SDN zones, with optional type, search, field, and limit filters to find specific inventory data.

Instructions

List cluster resources of any kind from /cluster/resources: nodes, guests, storage, pools and SDN zones. Use proxmox_list_guests for a friendlier guest list.

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

Input Schema

NameRequiredDescriptionDefault
typeNoResource type (default all)
limitNoMaximum number of results (default 1000)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=false, so safety is covered structurally. The description adds that results are a raw passthrough of /cluster/resources rather than a curated view, which is useful context, but it says nothing about result size, ordering, or how the limit interacts with truncation.

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, zero filler, with the scope and source endpoint front-loaded and the sibling redirect placed last where it is most actionable.

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 and annotations covering the read-only safety profile, the description needs only to establish scope and the data source, which it does. Minor gaps around pagination/truncation behavior keep it from a 5.

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 description coverage is 75%, so most parameters (type, limit, search) are already documented in the schema, and the description adds no parameter-level detail. Only 'fields' lacks a schema description, and the description does not compensate for it — 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 names a specific verb and resource ('List cluster resources'), enumerates the resource kinds covered (nodes, guests, storage, pools, SDN zones), and cites the backing endpoint /cluster/resources. It also explicitly distinguishes itself from proxmox_list_guests, so an agent can select between them 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 Guidelines4/5

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

It gives clear routing guidance: use this for the raw unified listing, use proxmox_list_guests for a friendlier guest list. It doesn't state exclusions or prerequisites (e.g. permissions), so it falls short of a full when/when-not treatment.

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