mcp-vmware

by Hokonoken

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

vmware_get_vm

Read-onlyIdempotent

Retrieve full details of a VMware VM including configuration, CPU/RAM, disks, NICs, guest IPs, and snapshot tree.

Instructions

Full details of a VM: config, CPU/RAM, disks, NICs, guest IPs, snapshots.

Returns a structured object with uuid, path, hardware_version, disks[], nics[], guest_ips[], snapshots[] (tree), resource_pool, folder, on top of the standard summary.

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": {
      "vm": "<vm>"
    },
    "name": "vmware_get_vm"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	Yes	Exact name or MoID (e.g. vm-123) of the VM

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=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe read operation. The description adds valuable context about the return structure and fields, going beyond annotations. 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?

Two sentences, no filler. The first sentence lists key items, the second specifies the structured object. Information is front-loaded and every word adds value.

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?

Given the presence of an output schema (though not shown), the description provides sufficient overview of return fields. The parameter is well-documented, annotations cover safety, and sibling tools are contextually irrelevant. No gaps remain.

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?

Schema provides 100% coverage for the single required parameter 'vm', with description 'Exact name or MoID (e.g. vm-123) of the VM'. The description does not add further parameter info but the baseline is 3 due to high schema coverage; however, the schema description itself is clear, and the tool description reinforces the scope, justifying a 4.

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 it provides 'Full details of a VM' listing specific components (config, CPU/RAM, disks, NICs, guest IPs, snapshots). This distinguishes it from sibling tools like vmware_list_vms which likely only return summaries or lists, and from other get tools focusing on different entities.

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 implies usage for retrieving detailed information about a single VM, but does not explicitly state when to use this tool versus alternatives (e.g., vmware_list_vms for listing). No exclusions or prerequisites are mentioned.

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