VMware-AIops

convert_vm_to_template

Convert a powered-off VM into a vSphere template for use as a clone source. The VM becomes a reusable template and can no longer be powered on.

Instructions

[WRITE] Convert a powered-off VM to a vSphere template.

After conversion the VM cannot be powered on — it serves as a clone source for deploy_vm_from_template.

Args: vm_name: Name of the VM to convert (must be powered off). target: Optional vCenter/ESXi target name from config.

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": {
      "vm_name": "<vm_name>"
    },
    "name": "convert_vm_to_template"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No
`vm_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.5.29May 29, 2026
Removedv1.5.28May 22, 2026
First observedv0.6.0Mar 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations indicate write, non-destructive, non-idempotent. The description adds that the converted VM cannot be powered on, providing context beyond annotations. It does not mention potential irreversibility or return format, but output schema exists.

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 concise, starting with '[WRITE]' prefix, then a clear action sentence, a note on post-conversion behavior, and parameter details. No wasted words.

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?

For a simple conversion tool, the description covers action, prerequisite, and outcome. It mentions the relationship with deploy_vm_from_template. Missing are permissions or error conditions, but output schema handles return info.

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%, but the description adds meaning for both parameters: 'vm_name' must be powered off, and 'target' is optional and from config. This compensates for the lack of schema descriptions.

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 description clearly states the tool converts a powered-off VM to a vSphere template, using specific verb and resource. It distinguishes from the sibling deploy_vm_from_template by noting the template serves as a clone source, establishing differentiation.

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 specifies the prerequisite (VM must be powered off) and the outcome (cannot be powered on). It implies use when a template is needed for cloning, but does not explicitly exclude alternatives like vm_clone or deploy_vm_from_ova.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.