Skip to main content
Glama

xo_v2v_list_esxi

Lists ESXi hosts configured in Xen Orchestra to identify VMware VM sources available for V2V migration to XCP-ng.

Instructions

List ESXi hosts configured in Xen Orchestra for V2V migration.

Returns the ESXi servers that XO can connect to for importing VMware VMs into XCP-ng. Add ESXi servers in XO → Settings → Servers.

Args: gateway_id: Target gateway (optional).

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

Input Schema

NameRequiredDescriptionDefault
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden; it does convey that results are the ESXi servers XO can actually connect to and that configuration happens elsewhere in XO. It omits whether the call is strictly read-only, what the returned fields look like, and how an empty or unreachable-server case behaves.

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?

The description is short and front-loaded: purpose first, return semantics second, practical setup hint third. The Args block is nearly redundant with the schema, but overall there is little waste.

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?

For a simple one-optional-parameter list tool with no output schema, the description covers purpose and setup but leaves the return shape and the effect of gateway_id unexplained. An agent can call it, but cannot fully predict the response.

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?

Schema coverage is 0% for the single gateway_id parameter, and the description only repeats 'Target gateway (optional)' without explaining what a gateway is or how it filters or routes the host list. That adds essentially nothing beyond the schema's own title and default.

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 ESXi hosts configured in Xen Orchestra') and scopes it to V2V migration, which distinguishes it from VM-listing siblings like xo_v2v_list_vmware_vms. It stops short of naming any sibling explicitly, so it lands at clear-but-not-differentiating.

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?

Usage is only implied by the V2V context and the note to add servers via XO → Settings → Servers, which serves as a prerequisite/empty-state hint. There is no explicit statement of when to call this versus the other xo_v2v tools 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