Skip to main content
Glama

List VMs and containers

proxmox_list_guests
Read-only

List Proxmox VMs and containers across a cluster, with status, node, CPU, memory, disk, uptime, tags, and pool details. Filter by type, node, status, tag, pool, or search, and sort by resource use.

Instructions

List virtual machines and containers across the cluster with status, node, CPU, memory, disk, uptime, tags and pool. Filter by type, node, status, tag, pool or a search string, and sort by resource use.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
tagNoOnly guests with this tag
nodeNoOnly guests on this node
poolNoOnly guests in this resource pool
sortNoSort order (default vmid); cpu/memory/disk/uptime sort highest first
typeNoOnly VMs (qemu) or only containers (lxc)
limitNoMaximum number of results (default 500)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
statusNoOnly guests in this state
templatesNoHow to treat templates (default include)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by enumerating the result payload fields and the sort direction semantics ('sort by resource use'), which matters since there is no output schema. It omits pagination/limit behavior and result-size caveats, so it is not fully complete.

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, front-loaded with what is returned before what can be filtered, with zero redundancy and no filler. The ordering matches how an agent would reason about the tool.

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?

For an 11-parameter, no-output-schema listing tool, the description covers the return payload and filtering surface well, which compensates for the absent output schema. It stops short of explaining pagination/limit interaction or the raw/templates toggle implications, which are left entirely to the schema.

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 91%, so all 11 parameters are already documented in the schema, including enums for type, status, sort, and templates. The description only restates the filter dimensions in prose and adds no format details, defaults, or interaction rules beyond what the schema provides. Baseline 3 applies.

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 and resource ('List virtual machines and containers across the cluster') and enumerates the returned fields (status, node, CPU, memory, disk, uptime, tags, pool). It is clearly distinguishable from unrelated siblings, though it never mentions proxmox_list_vms or proxmox_list_containers, so the agent must infer that this is the aggregate view over both.

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 filter dimensions (type, node, status, tag, pool, search) imply when the tool is appropriate — a filtered cluster-wide inventory — but there is no explicit 'use this when...' guidance, no stated exclusions, and no routing to the per-type siblings. Usage is inferable rather than stated.

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