vmware-mcp

by havu0

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Create Snapshot

vm_snapshot_create

Create a snapshot of a VMware virtual machine to preserve its current state and enable rollback if needed.

Instructions

Create a snapshot of a virtual machine. Do not use "/" in snapshot names. Note: may fail on running encrypted VMs due to vmrun limitations — stop the VM first if needed.

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": {
      "snapshot_name": "<snapshot_name>"
    },
    "name": "vm_snapshot_create"
  }
}

Input Schema

Name	Required	Description	Default
`vm`	No	VM name or .vmx path
`snapshot_name`	Yes	Name for the new snapshot

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden, and it does disclose a real edge-case failure ('may fail on running encrypted VMs due to vmrun limitations') plus a mitigation. Minor omissions such as success response or side effects on existing snapshots keep it just below a 5.

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 focused sentences with no filler. The core action is front-loaded, and the two warnings are placed immediately after, each earning 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?

For a simple two-parameter snapshot operation without an output schema, the description covers the main action, naming rules, and a failure mode. It does not explain why vm is optional or what happens if omitted, but this is a minor gap given the schema's clarity.

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 coverage is 100%, so parameters are well documented structurally. The description adds extra semantics by constraining snapshot_name (no '/') and relating VM state to success, going beyond the bare schema.

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 uses a specific verb ('Create') and resource ('snapshot of a virtual machine'), making the action unambiguous. It also distinguishes itself from sibling snapshot operations (revert, list, delete) by the create verb.

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?

It gives concrete operational guidance: avoid '/' in snapshot names, and stop running encrypted VMs before snapshotting if needed. It doesn't explicitly discuss alternatives, but the create-vs-management distinction among siblings is self-evident.

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