Skip to main content
Glama

vsphere_list_vms

List VMs in a vCenter inventory and filter by power state, datacenter, or cluster to locate the virtual machines needed for operations or troubleshooting.

Instructions

List all VMs in the vCenter inventory. Filter by power_state (all/poweredOn/poweredOff/suspended), datacenter, or cluster.

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

Input Schema

NameRequiredDescriptionDefault
clusterNo
datacenterNo
gateway_idNo
power_stateNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

B3.2/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 burden. 'List' implies a read, but the definition says nothing about pagination, ordering, result volume, or authentication/gateway requirements for a 4-parameter inventory call.

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?

Two tight sentences with the listing scope front-loaded and the filters second; nothing is redundant. It could be marginally tighter but no sentence is wasted.

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 no-annotation, no-output-schema tool with four parameters, the description covers the filtering surface but omits the meaning of gateway_id, return shape, and any default-behavior detail beyond the implied 'all'. Adequate but with clear gaps.

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 coverage is 0% and no parameter has an enum, so the description meaningfully compensates by enumerating power_state values (all/poweredOn/poweredOff/suspended) and naming datacenter and cluster filters. It leaves gateway_id entirely unexplained and gives no matching semantics (exact name vs. path) for the string filters.

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?

States a specific verb and resource ('List all VMs') plus scope ('vCenter inventory'), which separates it from the Proxmox/XO siblings by platform. It does not explicitly name a sibling to contrast with, so it stops short of a 5.

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 filtering sentence implies when the tool is appropriate (inventory listing narrowed by power state, datacenter, or cluster), but there is no explicit when-not guidance or routing to alternatives such as vsphere_get_vm for a single VM.

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