vmware-knight

deploy_linked_clone

Create a linked clone from a VM snapshot to provision test/dev environments with minimal storage and fast deployment.

Instructions

[WRITE] Create a linked clone from a VM snapshot — near-instant, minimal disk usage.

The clone writes to a copy-on-write delta over the source's base disk, so it depends on the source staying intact. Fastest provisioning for test/dev fleets; use vm_clone for fully independent copies. Requires the named snapshot — run vm_list_snapshots first. Returns a status string with the new clone name.

Input Schema

TableJSON Schema

Name	Required	Description
`cpu`	No	Override vCPU count; omit to keep the source's value.
`target`	No	vCenter/ESXi target from config.yaml; omit for the default.
`new_name`	Yes	Name for the new linked clone; must not already exist.
`power_on`	No	Power the clone on after creation (default False).
`memory_mb`	No	Override memory in MB; omit to keep the source's value.
`snapshot_name`	Yes	Clone base (from vm_list_snapshots).
`source_vm_name`	Yes	Source VM name (must have at least one snapshot).
`baseline_snapshot`	No	If set, snapshots the new clone with this name.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.12.10Sep 23, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations only state low-level hints (readOnly=false, destructive=false), so the description carries the behavioral burden. It discloses the copy-on-write mechanism, the source-dependency risk ('depends on the source staying intact'), and the return type ('status string with the new clone name'). This adds meaningful behavioral context beyond the annotations.

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 and front-loaded: purpose first, then behavior, use case, alternative, prerequisite, and return value. Every sentence earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 8 parameters, the output schema and 100% parameter coverage handle the details. The description adds exactly the missing context an agent needs: what the tool does, when to choose it, the critical source dependency, and the required snapshot workflow. Nothing essential is omitted.

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 100%, so parameters are fully described in the schema. The description adds context for snapshot_name/source_vm_name via the prerequisite and source-dependency note, but most parameter meaning is already present in the schema. Baseline 3 is appropriate.

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?

Description states a specific action ('Create a linked clone from a VM snapshot'), the core characteristics ('near-instant, minimal disk usage'), and explicitly differentiates from vm_clone ('use vm_clone for fully independent copies'). This makes the tool's role unmistakable among many VM-related siblings.

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?

Gives clear when-to-use guidance ('Fastest provisioning for test/dev fleets'), names the alternative for a different need (vm_clone), and states a hard prerequisite ('Requires the named snapshot — run vm_list_snapshots first'). It also implies a when-not via the dependency on the source staying intact.

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

Deploy Server