Skip to main content
Glama

vme_create_snapshot

Creates an HPE VME instance snapshot before migrations or risky changes, providing a recovery point and recording the write action in the audit log.

Instructions

Create a snapshot of an HPE VME instance. Use before migrations or risky changes.

Write operation — recorded in the audit log.

Args: instance_id: Morpheus instance ID. name: Snapshot name (e.g. "pre-migration-2026-09-09"). gateway_id: Target gateway (optional).

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": {
      "instance_id": "<instance_id>",
      "name": "<name>"
    },
    "name": "vme_create_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
gateway_idNo
instance_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description usefully discloses that this is a write operation recorded in the audit log, which the schema cannot convey. It omits other traits an agent would want before mutating state: required permissions, whether the instance must be running, and whether the call is synchronous or long-running.

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 purpose, then a caution, then a compact args block. Every line carries information; only the bare type restatements in the args list come close to redundancy.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the definition covers purpose, caution, audit logging and the three parameters. It leaves the caller without any idea of the return value (e.g. a snapshot ID) or failure modes, which the missing output schema makes more pressing.

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 0%, so the description carries the burden. It clarifies instance_id as a Morpheus instance ID, gives a naming convention example for name, and marks gateway_id optional, but never explains what gateway_id actually does or what happens when it is omitted.

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?

States a concrete verb+resource+platform: "Create a snapshot of an HPE VME instance." The platform qualifier implicitly separates it from the proxmox/vsphere/xo snapshot siblings, though it never names them to sharpen the distinction.

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?

"Use before migrations or risky changes" gives an actionable trigger for calling it. It stops short of stating exclusions or pointing at alternatives such as vme_list_snapshots for checking existing snapshots, so it is clear context rather than full routing guidance.

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