Skip to main content
Glama
Sign In
Proxmox VE MCP Server

Proxmox VE MCP Server

by MTDEV2312
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

list_vms

Retrieve all QEMU virtual machines on a specified Proxmox node.

Instructions

List all QEMU virtual machines on a specified node.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "node": "<node>"
    },
    "name": "list_vms"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'List all...' without detailing read-only nature, permissions, output format, pagination, or error behavior. The scope ('on a specified node') is helpful, but other behavioral traits are missing.

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?

The description is a single, clear sentence that immediately conveys the action and scope. There is no unnecessary information or redundancy.

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

Completeness2/5

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

Given the lack of output schema and annotations, the description should provide more context about what the tool returns and any preconditions. It does not explain the return format or potential errors, and there is no mention of required permissions. For a simple list tool, it is minimally acceptable but leaves important gaps.

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?

The input schema has no description for the 'node' parameter (0% coverage). The description mentions 'specified node' but does not explain what a node is, the expected format, or allowed values. Since schema coverage is zero, the description should compensate more but only offers a minimal hint.

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 the action ('List all'), the resource ('QEMU virtual machines'), and the scope ('on a specified node'). It distinguishes from sibling tools like list_containers (which lists containers) and get_vm_status (which targets a single VM).

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 the tool is used when you need to enumerate VMs on a particular node, but it does not explicitly mention when not to use it or suggest alternatives. There is no exclusion or comparison to sibling tools, so usage guidance is only implied.

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