vmware-knight

batch_linked_clone_vms

Batch provision multiple VMs as linked clones from a source snapshot, using copy-on-write to share the base disk while keeping the source intact.

Instructions

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

Clones share the source disk via copy-on-write, so the source must stay intact. Returns one dict per clone. Prefer batch_clone_vms for independent copies.

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
`cpu`	No	Override CPU count (optional).
`target`	No	Optional vCenter/ESXi target from config.
`power_on`	No	Power on each clone.
`vm_names`	Yes	Names for the new linked clones.
`memory_mb`	No	Override memory (optional).
`snapshot_name`	Yes	Clone base (from vm_list_snapshots).
`source_vm_name`	Yes	Source VM to clone from.
`baseline_snapshot`	No	Snapshot each clone with this name (optional).

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.12.10Sep 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations only indicate readOnlyHint=false and destructiveHint=false; the description adds meaningful behavioral context: clones share the source disk via copy-on-write, the source must remain intact, and each clone returns one dict. This goes beyond what the structured annotations convey.

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 compact, front-loaded with the core action, and each sentence earns its place: purpose, behavioral constraint, return shape, and sibling routing. No filler or redundant schema repetition.

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 tool with 8 parameters and a rich output schema, the description covers the critical non-obvious aspects: copy-on-write semantics, source immutability, return format, and the relevant alternative. It does not need to restate parameter details since the schema fully documents them.

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 description coverage is 100%, so the baseline is 3. The description does not add parameter-level meaning beyond the schema, though it reinforces the cloning mechanism tied to source_vm_name and snapshot_name.

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 a specific verb and resource: 'Batch create linked clones from a VM snapshot'. It clearly distinguishes itself from batch_clone_vms by noting the alternative is for independent copies, so an agent can tell them apart immediately.

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

Usage Guidelines5/5

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

It explicitly states when to use this tool over the sibling: 'Prefer batch_clone_vms for independent copies.' It also communicates a hard precondition—'the source must stay intact'—which informs safe usage.

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

Deploy Server