Skip to main content
Glama

xo_snapshot_vm

Create a snapshot of an XCP-ng VM using its VM ID and a snapshot name to preserve a restore point before changes or for backup.

Instructions

Create a snapshot of an XCP-ng VM.

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_id": "<vm_id>",
      "name": "<name>"
    },
    "name": "xo_snapshot_vm"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
vm_idYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, yet it only restates the action. It says nothing about whether the snapshot includes memory, whether the VM must be running or paused, whether the name must be unique, permission requirements, or side effects — all material for a mutating tool.

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?

A single front-loaded sentence with zero filler, so nothing is wasted. Its brevity is a virtue structurally even though the same brevity causes gaps captured in other dimensions.

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

Completeness2/5

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

For a mutating, multi-platform-adjacent tool with no annotations, no output schema, and 0% parameter documentation, one sentence is inadequate. An agent knows what to do at a high level but not how to populate the required arguments correctly or what behavior to expect.

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

Parameters1/5

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

Schema description coverage is 0% across three parameters, and the description mentions none of them. The snapshot's 'name' argument, the 'vm_id' target format, and the optional 'gateway_id' routing parameter are left entirely unexplained in both the schema and the description.

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') plus a platform qualifier ('XCP-ng VM'), which implicitly separates it from the proxmox/vme/vsphere snapshot siblings. It does not explicitly name or contrast those alternatives, so it falls short of a 5.

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 statement of when to use this tool, when not to, or which sibling snapshot tool to prefer for a given platform. The only guidance an agent can infer is that the target must be an XCP-ng VM, which comes from the platform word rather than any usage instruction.

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