vmware-knight

vm_create_snapshot

Create a VM snapshot before risky changes so you can revert if something goes wrong, then delete it later to reclaim space.

Instructions

[WRITE] Create a snapshot of a VM.

Returns a status string. Use this before a risky change so vm_revert_snapshot can undo it, then reclaim the space with vm_delete_snapshot — snapshots left for days grow delta disks and must not be treated as backups.

Input Schema

TableJSON Schema

Name	Required	Description
`memory`	No	Include memory state (heavier, allows resume).
`target`	No	vCenter/ESXi target name from config.
`quiesce`	No	Quiesce guest filesystem (requires running VMware Tools).
`vm_name`	Yes	VM to snapshot.
`description`	No	Optional description.
`snapshot_name`	Yes	Snapshot name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.12.10Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations (which are minimal), the description discloses that the tool returns a status string and warns about delta-disk growth. It does not elaborate on async behavior or failure modes, but the annotations and output schema cover the core write/safety profile.

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 compact, front-loaded with the action and return type, and every sentence serves a purpose. The lifecycle warning and sibling references add value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a create-snapshot tool with an output schema and a 100%-described input schema, the description provides the missing operational context: when to snapshot, how to undo, how to reclaim space, and why snapshots are not backups. Nothing essential is left unexplained.

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?

The input schema already documents every parameter, including defaults and descriptions, so the description carries little additional parameter-level semantics. It adds global context about snapshot lifecycle but does not deepen understanding of individual parameters.

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 and resource ('Create a snapshot of a VM') and immediately orients the agent by referencing the related revert and delete siblings. This makes the tool's purpose unambiguous and distinguishes it from nearby snapshot lifecycle tools.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool ('before a risky change') and when to follow up with vm_revert_snapshot and vm_delete_snapshot. It also warns against treating snapshots as backups, leaving no ambiguity about appropriate usage.

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

Deploy Server