Skip to main content
Glama

vme_list_instances

Lists all VMs managed by HPE VM Essentials (Morpheus) with status, cloud/zone, service plan, CPU, and memory details, and filters results by status, cloud, or gateway.

Instructions

List all VMs managed by HPE VM Essentials (Morpheus).

Returns name, status, cloud/zone, service plan, CPU and memory for each instance. HPE VME manages both KVM-native VMs and imported VMware VMs from the same console.

Args: status: Filter by VM status — "running", "stopped", or "all" (default). cloud: Filter by cloud/zone name (optional). gateway_id: Target gateway (optional if only one VME gateway exists).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vme_list_instances"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudNo
statusNoall
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the return payload (name, status, cloud/zone, service plan, CPU, memory) plus the gateway prerequisite. It leaves out pagination/result-limit behavior and any error or permission notes, which are the main remaining gaps for a read-only listing tool.

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?

Front-loaded with the action and resource, then return contents, then a short disambiguating note, then a clean Args block. Every sentence adds information; nothing is redundant padding.

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?

No output schema exists, and the description covers return fields, the three optional parameters, and the single-gateway fallback, which is enough to call it correctly. It stops short of pagination limits, filtering combination semantics, or what an empty result means.

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

Parameters4/5

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

Schema description coverage is 0%, but the Args block compensates well: it enumerates the status values ('running', 'stopped', 'all' with 'all' as default), explains cloud as a cloud/zone name filter, and clarifies gateway_id is optional when only one gateway exists. Minor gap: it doesn't say whether cloud is exact-match or substring, or what a gateway ID looks like.

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?

States a specific verb and resource ('List all VMs managed by HPE VM Essentials (Morpheus)') and scopes it to a named platform. The note that HPE VME manages both KVM-native and imported VMware VMs lets an agent distinguish this from sibling listers such as vsphere_list_vms or proxmox_list_vms.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this is the inventory call for VME-managed VMs, and the gateway_id note ('optional if only one VME gateway exists') gives one real prerequisite. There is no explicit 'use this instead of X' routing or statement of when not to use it, e.g. versus vme_get_instance for single-VM detail.

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