VMware-AIops

vm_create_snapshot

Idempotent

Create a snapshot of a VMware virtual machine to capture its current state, with optional memory inclusion and filesystem quiescing for consistent backups.

Instructions

[WRITE] Create a snapshot of a VM.

Args: vm_name: VM to snapshot. snapshot_name: Snapshot name. description: Optional description. memory: Include memory state (heavier, allows resume). quiesce: Quiesce guest filesystem (requires running VMware Tools). target: 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>",
      "snapshot_name": "<snapshot_name>"
    },
    "name": "vm_create_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`memory`	No
`target`	No
`quiesce`	No
`vm_name`	Yes
`description`	No
`snapshot_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.5.38Jun 12, 2026

addedInput schema / properties / quiesce

Added value: +{
+  "default": false,
+  "title": "Quiesce",
+  "type": "boolean"
+}

Addedv1.5.29May 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond annotations, the description discloses that memory snapshots are heavier and allow resume, quiesce requires VMware Tools, and target specifies the vCenter/ESXi target. However, it does not mention prerequisites like VM power state for memory snapshots.

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 very concise, front-loading the purpose with a single sentence and then listing parameters with brief explanations. Every sentence is informative with no wasted words.

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?

Given the complexity (6 parameters, related sibling tools, output schema exists), the description covers the main aspects. It explains parameter effects but could mention that a memory snapshot requires the VM to be powered on. Overall, very good.

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?

With 0% schema description coverage, the description must explain parameters. It provides useful explanations for memory, quiesce, and target, and clarifies vm_name and snapshot_name. While minimal, it adds meaning beyond the schema titles.

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 'Create a snapshot of a VM', providing a specific verb and resource. It distinguishes from sibling tools like vm_delete_snapshot and vm_list_snapshots by focusing on creation.

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

Usage Guidelines3/5

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

The description implies usage for creating snapshots but lacks explicit guidance on when to use this tool versus alternatives like vm_revert_snapshot or vm_delete_snapshot. No 'when not to' or alternative suggestions are provided.

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