Skip to main content
Glama

xo_v2v_list_vmware_vms

List VMware VMs on an ESXi host available for V2V migration to XCP-ng, using the ESXi server ID and an optional target gateway.

Instructions

List VMs on a VMware ESXi host available for V2V migration to XCP-ng.

Args: esxi_id: ESXi server ID (from xo_v2v_list_esxi). gateway_id: Target gateway (optional).

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": {
      "esxi_id": "<esxi_id>"
    },
    "name": "xo_v2v_list_vmware_vms"
  }
}

Input Schema

NameRequiredDescriptionDefault
esxi_idYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.4/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 disclosure burden, and it discloses very little. 'Available for V2V migration' implies server-side filtering of results, which is useful, but nothing is said about whether the call is read-only (only implied by 'List'), whether results are paginated, what happens with an invalid ESXi ID, or how gateway_id changes discovery. For a zero-annotation tool this is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One scoping sentence followed by a compact Args block – front-loaded and easy to scan, with no filler. The only wasted token is '(optional)', which the schema's default null already conveys.

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?

With two simple parameters and no output schema, an agent can call this correctly from what is provided, and the upstream-call hint covers the main failure mode (where esxi_id comes from). It remains thin on return contents and on how gateway_id affects reachability, which matters for a cross-hypervisor discovery step.

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 0%, so the description must add the meaning, and it partially does: it identifies the source of esxi_id and clarifies that gateway_id is a target gateway. However, 'Target gateway (optional)' merely restates the default already visible in the schema and never explains why a bastion/gateway is needed to enumerate an ESXi host, which is the non-obvious part.

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 scoped tightly: 'List VMs on a VMware ESXi host available for V2V migration to XCP-ng.' The 'available for V2V migration' qualifier meaningfully separates it from a general XCP-ng VM lister. It stops short of a 5 because it never states how it differs from other VMware-facing listers in the catalog.

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

Usage Guidelines4/5

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

'esxi_id: ESXi server ID (from xo_v2v_list_esxi)' embeds the prerequisite call in the parameter note, giving the agent a clear workflow ordering rather than just a type. There are no when-not-use conditions or explicit alternative routing, which keeps it out of 5 territory.

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