mcp-vmware

by Hokonoken

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

vmware_host_storage

Read-onlyIdempotent

List paginated storage details for an ESXi host: HBA adapters and LUNs with multipath paths.

Instructions

Storage of a host (equivalent of esxcli storage): HBA adapters and paginated LUNs with multipath paths.

In json: {host, adapters:[...], total, count, offset, has_more, next_offset, luns:[{canonical_name, model, type, capacity, operational_state, paths}]}. Rescan with vmware_host_rescan_storage (host.config).

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

Input Schema

Name	Required	Description	Default
`host`	Yes	Name of the ESXi host
`limit`	No	Maximum number of LUNs
`offset`	No	Pagination offset for LUNs
`response_format`	No	markdown (default, compact table) or json (full structure)	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate readOnly and idempotent behavior. The description adds value by detailing the returned data structure (HBA adapters, paginated LUNs, fields like capacity and paths), providing context beyond the annotations.

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 reasonably concise, with two clear sections: purpose and data structure. It avoids unnecessary details but could be better formatted with bullet points or clearer separation.

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

Completeness4/5

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

The description covers the tool's purpose and output structure, compensating for the presence of an output schema. It is sufficient for a read-only listing tool, though it slightly lacks explanation of HBA adapter details.

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 100%, so description provides minimal added value for parameters. It mentions pagination indirectly via the JSON structure but does not elaborate on limit or offset beyond the schema.

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?

The description clearly states the tool retrieves storage information for a host, including HBA adapters and paginated LUNs with multipath paths, distinguishing it from other host-related tools.

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 description provides a hint about an alternative tool (vmware_host_rescan_storage) for a different action, but lacks explicit guidance on when to use this tool versus siblings like vmware_list_hosts or vmware_host_health.

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