vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Suspend VM

vm_suspend

Suspend a VMware virtual machine by preserving its current state to disk, enabling you to pause operations and resume precisely where you stopped. Select soft for graceful suspension or hard for immediate stop.

Instructions

Suspend a virtual machine, preserving its current state to disk. Warning: encrypted VMs may not resume via vmrun after suspend — use vm_stop instead if unsure.

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

Input Schema

Name	Required	Description	Default
`vm`	No	VM name from config, or full .vmx path. Uses default_vm if omitted
`mode`	No		soft

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A3.8/5.0

Behavior3/5

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

There are no annotations, so the description carries the full behavioral disclosure burden. It does disclose a key trait (state is saved to disk) and a concrete risk (encrypted VMs may not resume via vmrun), but it omits mode semantics, reversibility, and what happens to the VM after suspension beyond the warning.

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 with no filler; the action is stated first and the warning is a meaningful, necessary addition. Every sentence earns its place.

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

Completeness3/5

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

The core purpose and a critical caveat are present, and no parameters are required, so a default invocation is feasible. But mode semantics are unexplained and there is no guidance distinguishing suspend from vm_pause, leaving the definition only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: the vm parameter is documented, but mode is just an enum without explanation. The description adds no meaning for soft vs hard modes, so the agent has to guess which mode to use or what the difference is.

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 names a specific operation and resource — suspending a virtual machine — and clarifies the defining behavior: preserving current state to disk. The warning also explicitly positions it against vm_stop, helping distinguish it from power-off and other VM-state-changing siblings.

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

Usage Guidelines4/5

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

The warning gives an explicit when-not-to-use condition (encrypted VMs) and names vm_stop as the safer alternative, which is strong routing guidance. However, it does not contrast with vm_pause or describe when suspend should be preferred over pause or reset.

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