vmware-mcp

Overview Schema Source Related Servers Discussions Admin

List Snapshots

vm_snapshot_list

List every snapshot of a VMware VM in a tree view, showing hierarchy to simplify review of snapshot chains and restore points.

Instructions

List all snapshots of a virtual machine in tree format.

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

Input Schema

Name	Required	Description	Default
`vm`	No	VM name or .vmx path

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are present, so the description carries the behavioral burden. 'List' implies a read-only operation and 'tree format' indicates output structure, but the description does not address VM power state requirements, error conditions, or behavior when the vm parameter is omitted.

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 ten-word sentence with the action front-loaded and no filler. Every element—'all', 'virtual machine', 'tree format'—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 tool is simple, but the description says 'of a virtual machine' while the schema marks vm as optional, leaving the no-vm case unexplained. With no output schema, a bit more detail about what the tree contains would make the tool more 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% because the only parameter, vm, is described as 'VM name or .vmx path'. The description adds no parameter-level details beyond what the schema already provides, so the baseline of 3 applies.

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 'List' and a clear resource 'snapshots of a virtual machine', plus the 'tree format' detail. It is easily distinguished from sibling operations like vm_snapshot_create, vm_snapshot_revert, and vm_snapshot_delete.

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 description makes the primary use case clear: call this when you need to view the snapshots of a VM. It provides no explicit exclusions or alternative tool names, but no other sibling performs this exact function, so the context is sufficient.

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