Skip to main content
Glama

xo_list_vms

Lists virtual machines across XCP-ng pools managed by Xen Orchestra, with optional gateway and power-state filters for inventory and monitoring.

Instructions

List all VMs on XCP-ng pools managed by Xen Orchestra.

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": "xo_list_vms"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
power_stateNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.7/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 the full behavioral burden, but it only states the listing scope. It does not confirm that this is a read-only operation, describe return or pagination behavior, or explain how results are constrained by the gateway and power-state filters.

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 front-loaded sentence with no wasted wording. It states the resource and scope efficiently.

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?

For a two-parameter list tool with no annotations and no output schema, the description is too thin. It leaves both parameters unexplained and gives an agent no guidance about filtering, return shape, or alternatives, so an agent could call it but not confidently use its options.

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

Parameters1/5

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

Both parameters have zero schema description coverage, and the description never mentions gateway_id or power_state. It therefore adds no meaning about whether gateway_id scopes to a specific Xen Orchestra connection or what power_state values like "all" mean.

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?

The description gives a specific verb and resource ("List all VMs") and a clear platform scope ("XCP-ng pools managed by Xen Orchestra"). That scope meaningfully distinguishes it from sibling list tools for Proxmox, vSphere, and VMware VMs, though it does not explicitly name those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description identifies the platform but offers no explicit guidance on when to use this tool instead of the other VM-listing tools. It also does not explain when to use the optional gateway_id or power_state filters, or any exclusions.

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