VMware-Monitor

list_vm_snapshots

Read-onlyIdempotent

List all snapshots for a given VM to view names, timestamps, states, and nesting hierarchy; read-only operation.

Instructions

[READ] List all snapshots of one VM, including the nesting hierarchy.

Returns the list envelope, one row per snapshot with name, description, created timestamp, state and level (0 = root; children are level+1). Empty items with truncated False means the VM genuinely has no snapshots. Read-only — creating, reverting and deleting snapshots live in vmware-aiops.

Use this for one known VM; prefer find_aging_snapshots to sweep the whole inventory for old or sprawling snapshots. Get the name from list_virtual_machines first — an unknown name returns a teaching error.

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": "list_vm_snapshots"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No	vCenter/ESXi target from config (default if omitted).
`vm_name`	Yes	Exact name of the virtual machine.

Schema Changelog

Changes observed during successful MCP inspections.

Addedv2.2.0Oct 15, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine beyond-annotation context: the return envelope shape, level semantics, empty-items meaning, and the teaching-error behavior on unknown names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the [READ] marker and purpose, then return semantics, then routing guidance. A couple of phrases (the truncated-False explanation) are slightly verbose but each sentence carries useful information.

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 read-only list tool with no output schema, the description supplies return structure, level semantics, empty-result meaning, error behavior, and alternative-tool routing. Only minor gaps remain, such as pagination/truncation mechanics beyond the empty-items note.

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 coverage is 100%, so both parameters (target, vm_name) are already documented in the schema. The description notes vm_name must come from list_virtual_machines and that an unknown name yields a teaching error, which is mild added meaning over the schema baseline.

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?

Specific verb+resource ('List all snapshots of one VM') with explicit scope ('including the nesting hierarchy'). It distinguishes itself from siblings by naming find_aging_snapshots as the sweep alternative and confining itself to one known VM.

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?

Clearly states when to use this (one known VM) versus find_aging_snapshots (whole-inventory sweep), and routes the agent to list_virtual_machines for the name. Lacks explicit when-not conditions beyond the sibling contrast, but the context is clear.

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