VMware-AIops

vm_clean_slate

Destructive

Powers off a VM and reverts it to a specified snapshot, restoring a clean baseline state. Use to reset lab or dev VMs after tasks.

Instructions

[WRITE] Revert a VM to its baseline snapshot (Clean Slate).

Powers off the VM first if it is running, then reverts to the named snapshot. Use this to reset a lab/dev VM to a clean starting state after a task completes.

Args: vm_name: Name of the VM to revert. snapshot_name: Snapshot name to revert to (default: "baseline"). target: Optional vCenter/ESXi target name from config.

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": {
      "vm_name": "<vm_name>"
    },
    "name": "vm_clean_slate"
  }
}

Input Schema

Name	Required	Default
`target`	No
`vm_name`	Yes
`snapshot_name`	No	baseline

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.29May 29, 2026
Removedv1.5.28May 22, 2026
Addedv1.5.18May 4, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds behavioral details beyond annotations: 'Powers off the VM first if it is running, then reverts to the named snapshot.' This supplements the destructiveHint=true annotation. No contradictions with annotations.

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 concise: a titleline, two explanatory sentences, and an Args block. Each sentence adds value with no redundancy.

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?

The description covers purpose, behavior, and parameters adequately for a VM reset tool. It could explicitly mention that the snapshot must exist or error conditions, but it is sufficient given the output schema is present.

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?

Despite 0% schema description coverage, the description includes an Args block explaining all three parameters: vm_name (required), snapshot_name (default 'baseline'), and target (optional vCenter/ESXi target). This adds meaning beyond the input 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 clearly states 'Revert a VM to its baseline snapshot (Clean Slate)' using a specific verb and resource, distinguishing it from the sibling general revert tool vm_revert_snapshot by specifying the baseline snapshot and including the power-off behavior.

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 says 'Use this to reset a lab/dev VM to a clean starting state after a task completes,' providing clear context for when to use it. However, it does not explicitly state when not to use it or compare with alternatives like vm_revert_snapshot.

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