Skip to main content
Glama

vsphere_create_snapshot

Create a vSphere VM snapshot for backup, rollback, or change protection; quiescing is attempted automatically when VMware Tools is running.

Instructions

Create a snapshot of a vSphere VM. Quiescing is attempted automatically when VMware Tools is running.

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": {
      "name": "<name>",
      "snapshot_name": "<snapshot_name>"
    },
    "name": "vsphere_create_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
memoryNo
gateway_idNo
descriptionNo
snapshot_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does add one genuinely useful trait — quiescing is attempted automatically when VMware Tools is running, and only attempted, so it may silently not happen. But for a mutation tool it omits permissions required, whether the snapshot is reversible/removable, impact of the memory flag (stun/IO cost), expected latency, and the return value.

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?

Two short sentences, front-loaded with the action, with no filler. The brevity is appropriate in form but reflects under-specification rather than tight editing, so it stops short of a 5.

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?

Placeholder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five parameters, so the description must compensate and does not. It never explains the distinction between "name" and "snapshot_name" (VM identifier vs. snapshot label), nor what "memory" (default false) or "gateway_id" control. Only the implicit association of "name" with the VM is conveyed.

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?

The description gives a specific verb and resource ("Create a snapshot of a vSphere VM"), which is enough to distinguish it from snapshot tools on other hypervisors (proxmox/vme/xo) and from other vsphere_* tools that list, get, or power-manage VMs. It does not explicitly name an alternative, but the platform qualifier carries the differentiation.

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?

There is no guidance on when to use this tool versus other snapshot or VM lifecycle tools, no stated prerequisites (VM power state, permissions, whether snapshots can be taken on a powered-off VM), and no note about what to do on failure. The only condition given is about quiescing, which is a behavior, not a usage rule.

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

Deploy Server

Other Tools