Skip to main content
Glama
k-krawczyk

proxmox-mcp-server

by k-krawczyk

List VMs

pve_list_vms
Read-only

List QEMU VMs in a Proxmox cluster; specify a node to list only VMs on that node.

Instructions

List QEMU VMs. With a node, lists that node directly; without one, returns every VM in the cluster from the resource index.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds the key behavioral distinction of node parameter affecting scope. It does not contradict annotations and provides additional context beyond what annotations convey.

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 the purpose. No redundant or wasted words. Every sentence earns its place.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple with one optional parameter. The description adequately covers the two usage modes. No output schema is needed for a list operation, and the description is sufficient for the complexity.

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

Parameters4/5

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

Schema description coverage is 0%, so the description carries the full burden for the 'node' parameter. It explains the effect of providing or omitting the node parameter, adding meaning beyond the bare schema definition of a string.

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 clearly states it lists QEMU VMs and distinguishes between two modes: with a node (node-specific) and without (cluster-wide from resource index). This differentiates it from sibling tools like 'pve_list_containers' and 'pve_cluster_resources'.

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 gives context on when to use each mode (node vs no node) but does not explicitly state when not to use this tool or mention alternatives. It provides some guidance but lacks exclusions or comparisons to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/k-krawczyk/proxmox-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server