Skip to main content
Glama
Sign In
vmware-mcp

vmware-mcp

by havu0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get VM IP

vm_get_ip

Retrieve the IP address of a running VMware virtual machine by name or .vmx path, with an option to wait until an IP address becomes available.

Instructions

Get the IP address of a running virtual machine.

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

Input Schema

NameRequiredDescriptionDefault
vmNoVM name from config, or full .vmx path. Uses default_vm if omitted
waitNoWait/poll until IP is available

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the main behavioral burden. It conveys a non-mutating read action and the 'running' precondition, but it does not disclose what happens when the guest has no VMware Tools, whether the IP may be unavailable initially, or how the optional waiting behavior interacts with that.

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 a single precise sentence with no filler, no repetition, and the key resource is front-loaded. Every word earns its place.

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?

Given the low complexity, 100% schema parameter coverage, and no output schema, the description plus schema is nearly complete. The agent knows what to retrieve, what the VM parameter means, and that wait can poll for the IP, though a bit more behavioral context would make it fully self-contained.

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 description coverage is 100%, so the baseline is 3 because the schema already documents the vm and wait parameters. The description itself adds no parameter-level meaning beyond saying the subject is a VM.

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?

The description uses a specific verb and resource: 'Get the IP address' of a virtual machine. This is clearly distinct from lifecycle and guest-command siblings, though it does not explicitly name or contrast any sibling tool.

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 phrase 'of a running virtual machine' implies a precondition and suggests this is a read-only network retrieval tool. However, it provides no explicit when-to-use or when-not-to-use guidance, no named alternatives, and no exclusions.

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