VMware-AIops

batch_linked_clone_vms

Batch create linked clones from a VM snapshot using copy-on-write. Specify source VM, snapshot, and names for clones. Optionally override CPU, memory, power on, and add a baseline snapshot.

Instructions

[WRITE] Batch create linked clones from a VM snapshot (fastest batch provisioning).

Each clone shares the source disk via copy-on-write.

Args: source_vm_name: Source VM to clone from. snapshot_name: Snapshot to use as clone base. vm_names: List of names for the new linked clones. cpu: Override CPU count (optional). memory_mb: Override memory (optional). power_on: Power on each clone. baseline_snapshot: Create a new snapshot on each clone (optional). 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": {
      "source_vm_name": "<source_vm_name>",
      "snapshot_name": "<snapshot_name>",
      "vm_names": "<vm_names>"
    },
    "name": "batch_linked_clone_vms"
  }
}

Input Schema

Name	Required	Description	Default
`cpu`	No
`target`	No
`power_on`	No
`vm_names`	Yes
`memory_mb`	No
`snapshot_name`	Yes
`source_vm_name`	Yes
`baseline_snapshot`	No

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?

The description explicitly states '[WRITE]' indicating mutation, and explains the copy-on-write sharing behavior. Annotations (readOnlyHint=false, destructiveHint=false) are consistent with the write operation. No contradictions. The description adds valuable context about the disk sharing mechanism beyond annotations.

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 description is two paragraphs: a summary line, a behavioral note, and a parameter list. It is mostly concise but repeats parameter names unnecessarily in the bullet list. Front-loading is good with the summary. Could be slightly tighter but overall efficient.

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?

The description covers purpose, parameters, and key behavioral info (copy-on-write). It does not mention prerequisites (e.g., source VM and snapshot existence) or error conditions. Given the tool has an output schema (so return values are documented elsewhere) and annotation depth, it is largely adequate for an agent to use correctly.

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

Parameters5/5

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

With 0% schema description coverage, the description provides a bullet list explaining each of the 8 parameters, including optional overrides and defaults. This adds substantial meaning beyond the schema's name and type alone, fully compensating 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 opens with '[WRITE] Batch create linked clones from a VM snapshot (fastest batch provisioning),' which clearly states the action (batch create), resource (linked clones from VM snapshot), and key differentiator (fastest). This distinguishes it from sibling tools like batch_clone_vms (likely full clones) and deploy_linked_clone (single clone).

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 implies usage for fast batch provisioning by mentioning 'fastest batch provisioning' and specifying linked clones via copy-on-write. However, it does not explicitly state when to use this tool over alternatives or provide when-not-to-use guidance. It lacks explicit exclusions or comparisons with siblings like batch_clone_vms.

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