mcp-vmware

Overview Schema Source Related Servers Discussions Admin

vmware_get_host

Read-onlyIdempotent

Retrieve comprehensive details of an ESXi host, including connection state, uptime, hardware, running VMs, and mounted datastores.

Instructions

Details of an ESXi host: state, uptime, hardware, hosted VMs, mounted datastores.

Returns a JSON {name, moid, connection_state, power_state, in_maintenance, in_quarantine, boot_time, uptime_hours, version, model, cpu, memory, vms:[...], datastores:[...], networks:[...]}.

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": {
      "host": "<host>"
    },
    "name": "vmware_get_host"
  }
}

Input Schema

Name	Required	Description	Default
`host`	Yes	Host name (see vmware_list_hosts)

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, and non-destructive. The description adds the exact output structure and fields returned, providing behavioral context beyond annotations. No contradiction.

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?

Two sentences: first states purpose and scope, second enumerates output fields. No fluff, every word earns its place. Front-loaded with key purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only detail tool, it covers purpose, input, and output clearly. Has output schema and description lists fields. No missing context for proper invocation.

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

Parameters4/5

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

Single 'host' parameter with schema description that references vmware_list_hosts, adding practical guidance. With 100% schema coverage, the description adds value by telling how to find valid host names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it returns details of an ESXi host including state, uptime, hardware, VMs, and datastores. Distinguishes from sibling tools like vmware_list_hosts (list) and vmware_host_health (specific subsystem).

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?

Implies usage after identifying a host from vmware_list_hosts but does not explicitly state when to use vs alternatives like vmware_get_vm or vmware_host_advanced_settings. No when-not or exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.