Skip to main content
Glama

vme_convert_image

Convert virtual disk images between formats such as VMDK and QCOW2, enabling VMware-to-VME migrations without manual image rework. Runs asynchronously on the Morpheus appliance.

Instructions

Convert a virtual image to a different disk format.

Key tool for VMware-to-VME migrations: converts VMDK images to QCOW2 (KVM-native format) without manual intervention. The conversion runs asynchronously on the Morpheus appliance.

Write operation — recorded in the audit log.

Args: image_id: Virtual image ID (from vme_list_virtual_images). format: Target format — "qcow2", "vmdk", "raw", or "vhd". 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": {
      "image_id": "<image_id>",
      "format": "<format>"
    },
    "name": "vme_convert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYes
image_idYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does usefully disclose that the conversion is asynchronous and audited as a write operation. It omits whether the source image is preserved, whether the conversion is reversible, how to poll completion status, and what permissions are required — significant gaps for a mutating, long-running operation.

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?

The structure is strong — one-line summary, migration context, async/write notes, then per-argument docs — and it is front-loaded with the core purpose. It is slightly padded (the migration framing repeats the purpose line) but no sentence is genuinely wasteful.

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 three-parameter mutation with no annotations and no output schema, the definition covers purpose, async behavior, and argument meanings adequately. It still leaves the agent without guidance on tracking the async result or on source-image fate, which matters for correct invocation.

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 coverage is 0%, so the description must compensate, and it mostly does: it explains image_id's provenance and supplies the allowed format values (qcow2, vmdk, raw, vhd) that the schema lacks as an enum. gateway_id is only described as "Target gateway (optional)," leaving its selection criteria and default behavior unexplained.

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?

The opening sentence names a specific verb and resource ("Convert a virtual image") and the following lines narrow the scope to VMDK→QCOW2 migration, which distinguishes it from the sibling read/list tools such as vme_list_virtual_images. An agent can tell what this does without opening the schema.

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?

It gives a clear usage context ("Key tool for VMware-to-VME migrations") and routes the agent to vme_list_virtual_images for obtaining the image_id. It stops short of stating when not to use it or naming an alternative conversion path, so it is clear context rather than explicit when/when-not 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