Skip to main content
Glama

vme_list_snapshots

List all snapshots for an HPE VME instance, optionally scoped to a gateway, to help review restore points before recovery or rollback.

Instructions

List all snapshots for an HPE VME instance.

Args: instance_id: Morpheus instance ID. 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": "vme_list_snapshots"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
instance_idYes

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?

No annotations are supplied, so the description carries the full burden. It implies a read-only operation via 'List', but says nothing about permissions required, pagination or result limits, ordering, or what happens when the instance or gateway is invalid. The parenthetical '(optional)' on gateway_id is the only behavioral detail offered.

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?

One-line purpose followed by a compact Args block, front-loaded with the action. Nothing is padded, though the Args restatement of parameter names is close to duplicating the schema's titles.

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 two-parameter read tool with no output schema and no annotations, the minimum needed to invoke it is present: what it lists and the required ID. It is still incomplete on return shape and pagination, and on the meaning of the optional gateway scoping, which an agent would need in practice.

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 description coverage is 0%, so the description must compensate, and it does partially: it tells the agent that instance_id is a 'Morpheus instance ID' and that gateway_id is an optional target gateway. However it never explains how to obtain a gateway_id or what changes when one is supplied, leaving half the semantics thin.

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 specific verb and resource ('List all snapshots') scoped to an HPE VME instance, which cleanly separates it from write-side siblings such as vme_create_snapshot. It stops short of naming any sibling or describing the result set, so it is clear but not fully differentiated.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites, and no mention of what to do if the instance has no snapshots. The only directional signal is the implicit 'list' verb, matching the calibration case that scored 2 for lacking usage 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