Skip to main content
Glama
Sign In
vmware-mcp

vmware-mcp

by havu0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start VM

vm_start

Start a VMware virtual machine using a configured name or .vmx path. Select GUI or headless mode, and wait for the guest to report an IP address when needed.

Instructions

Start a VMware 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_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
vmNoVM name from config, or full .vmx path. Uses default_vm if omitted
guiNoShow VM window (true) or headless (false)
wait_for_ipNoWait until guest tools report an IP address after starting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Start a VMware virtual machine,' with no mention of side effects, default GUI behavior, whether it waits for boot, or what happens on failure.

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 a single, front-loaded sentence with no filler or repetition beyond the title. It is highly concise, even if it sacrifices informative content, which is penalized in other dimensions.

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

Completeness2/5

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

For a lifecycle-changing operation with no annotations and no output schema, this description is too thin. It does not explain the power-state transition, the headless/GUI option, the wait-for-IP behavior, or how this relates to guest operations and other VM lifecycle tools.

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%, and the schema already explains vm, gui, and wait_for_ip clearly. The description adds no parameter-level meaning, but the baseline of 3 applies because the schema does the necessary work.

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 clear verb ('Start') and a specific resource ('a VMware virtual machine'), so the core action is unambiguous. It is distinguishable from sibling tools like vm_stop or vm_reset by the verb, though it does not explicitly contrast itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance about when to use this tool versus alternatives like vm_suspend, vm_reset, or vm_unpause. The description does not mention prerequisites, state requirements, or typical scenarios, so the agent receives no routing help.

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