vmware-mcp

Overview Schema Source Related Servers Discussions Admin

Delete Snapshot

vm_snapshot_delete

Delete a virtual machine snapshot to free storage or revert to a previous state. Optionally remove child snapshots to clean up entire snapshot trees.

Instructions

Delete a snapshot from a virtual machine.

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

Input Schema

Name	Required	Description
`vm`	No	VM name or .vmx path
`snapshot_name`	Yes	Snapshot name to delete
`delete_children`	No	Also delete child snapshots

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 30, 2026

TDQS

B3.1/5.0

Behavior2/5

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

The description discloses that the action is destructive, which is implied by 'delete,' but with no annotations it carries full responsibility for behavioral context. It does not state irreversibility, what happens to child snapshots by default, or any side effects on the VM.

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?

A single clear sentence with no filler. It front-loads the core action and resource immediately.

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 schema covers all parameters with descriptions and defaults, and the purpose is clear. However, without annotations or an output schema, the description leaves behavioral and usage context thin for a destructive VM operation.

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 parameters like snapshot_name, vm, and delete_children are already documented. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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?

States an unambiguous verb and resource: delete a snapshot from a VM. It is clearly distinct from create/revert/list snapshot operations, though it does not explicitly name those siblings.

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?

No guidance is given about when to use this tool instead of vm_snapshot_create, vm_snapshot_revert, or vm_snapshot_list. The description does not mention prerequisites, when deleting children is appropriate, or when not to delete a snapshot.

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