Skip to main content
Glama

vme_list_virtual_images

Lists available HPE VME virtual images (templates, ISOs, uploads) so you can find the image ID before converting a VMware VMDK for migration.

Instructions

List available virtual images in HPE VME (templates, ISOs, uploaded images).

Use before vme_convert_image to find the image ID of a VMware VMDK that needs conversion for migration.

Args: image_type: Filter by type (optional). gateway_id: Target gateway (optional).

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_virtual_images"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateway_idNo
image_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description must disclose behavior; it implies a read-only listing and says results can identify an image ID, which is useful. It omits permissions/auth, pagination/limits, whether gateway scoping changes availability, and whether 'available' means accessible or unused.

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?

The description is front-loaded: purpose first, then the key downstream use, then the two parameters. It contains no filler sentences and the Args block is compact.

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 list tool with no annotations, no output schema, and bare schema, the description is minimally complete: it covers purpose, one workflow, and both parameters. It still lacks result fields, pagination/limits, and valid filter values, which an agent needs without an output schema.

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 full parameter documentation. It labels both optional parameters, saying image_type filters by type and gateway_id is a target gateway, but it gives no allowed image_type values, formats, or precise effect of gateway_id.

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 first sentence states a specific verb and resource ('List available virtual images in HPE VME') and enumerates object types (templates, ISOs, uploaded images). It also relates the tool to vme_convert_image, so an agent can tell what it is for, though it does not explicitly distinguish it from other list_* siblings beyond the resource name.

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?

The description gives a concrete use case: call this before vme_convert_image to find the image ID of a VMDK for migration. It does not state when not to use it or name alternative list/search tools, but the context is clear for the main workflow.

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