Skip to main content
Glama

vsphere_list_hosts

List all ESXi hosts in the vCenter inventory with CPU, memory, and connection state, optionally filtered by cluster or datacenter.

Instructions

List all ESXi hosts in the vCenter inventory with CPU, memory, and connection state.

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

Input Schema

NameRequiredDescriptionDefault
clusterNo
datacenterNo
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; the word 'List' plus 'inventory' implies a non-destructive read, and it discloses that results include CPU, memory, and connection state. It says nothing about permissions needed, whether results span all datacenters by default, pagination, or result volume for large inventories.

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?

A single front-loaded sentence with no filler; the returned fields are attached directly to the purpose statement. It is efficiently written, though its brevity contributes to the missing filter and behavior detail.

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 three-parameter tool with no annotations and no output schema, the definition should explain the filter parameters and the scope of the listing. It partially covers return fields but leaves the entire parameter surface and safety/behavior profile unaddressed.

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 description coverage is 0% and the description never mentions the cluster, datacenter, or gateway_id parameters, so nothing explains that these are optional scoping filters or how they combine. The phrase 'in the vCenter inventory' marginally implies no default filtering, but that is weak compensation for three fully undocumented parameters.

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 ESXi hosts in the vCenter inventory') and even names the attributes returned (CPU, memory, connection state). That is enough to separate it from vsphere_list_vms on resource type, though the description never explicitly contrasts the two.

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?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives among the many sibling list tools, and no prerequisites such as which gateway or datacenter context is needed. The only implicit cue is 'List all', which suggests an unfiltered enumeration.

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