Skip to main content
Glama
Sign In
mcp-vmware

mcp-vmware

by Hokonoken
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

vmware_list_clusters

Read-onlyIdempotent

List VMware clusters with HA/DRS status, hosts, and aggregated CPU and memory capacity, output in markdown or JSON.

Instructions

Lists the clusters: HA/DRS, hosts, aggregated CPU/RAM capacity.

In json: {count, clusters:[{name, moid, hosts, ha_enabled, drs_enabled, drs_behavior, total_cpu_mhz, total_memory, effective_hosts}]}. In markdown: table.

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

Input Schema

NameRequiredDescriptionDefault
response_formatNomarkdown (default, compact table) or json (full structure)markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds behavioral context: 'aggregated CPU/RAM capacity' and details on output structure (JSON fields and markdown table). No contradictions.

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?

The description is concise: two sentences front-loaded with purpose, followed by output format details. Every sentence adds value without redundancy.

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 simple list tool with one optional parameter, the description covers the output structure comprehensively. Even without an explicit output schema shown, the description provides the JSON structure and markdown table detail, making it complete.

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 the baseline is 3. The description adds examples of output content but does not significantly extend parameter semantics beyond the schema's description of 'response_format'.

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 'Lists the clusters: HA/DRS, hosts, aggregated CPU/RAM capacity', specifying the resource and scope. It distinguishes from sibling list tools (e.g., vmware_list_hosts, vmware_list_datastores) by focusing on clusters.

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 does not explicitly advise when to use this tool versus alternatives like vmware_get_cluster_config or vmware_drs_recommendations. Usage context is implied by listing clusters, but no explicit guidance is given.

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