Skip to main content
Glama

proxmox_list_vms

List all virtual machines on a Proxmox cluster and filter results by node or status (running, stopped, or all) to inspect and manage VM inventory.

Instructions

List all VMs on a Proxmox cluster. Filter by node or status (running/stopped/all).

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

Input Schema

NameRequiredDescriptionDefault
nodeNo
statusNoall
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and does little: "List" implies a read-only operation, but nothing is said about authentication, pagination, result size, or what fields each VM entry contains. With no output schema either, the behavior is largely undisclosed.

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 short sentences, the scoping statement first and the filtering options second. No filler or 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?

The core listing behavior and status filter are covered, but the undocumented gateway_id parameter and the absence of any return-shape or pagination information leave real gaps for a tool with no annotations and no output 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 coverage is 0%, so the description is the only source of parameter meaning, and it does add value by enumerating the allowed status values (running/stopped/all) that the schema leaves as a bare string. However, gateway_id is never mentioned, leaving one of three parameters completely undocumented.

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 all VMs on a Proxmox cluster"), which is unambiguous and inherently separates it from the vsphere_list_vms and xo_list_vms siblings by platform. It stops short of any explicit differentiation statement, but the scope is clear.

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 description implies usage via the filtering options (node, status) but never says when to choose this over another list tool or what prerequisites exist. Guidance 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