Skip to main content
Glama
CyberKnightLabs

vmware-knight

by CyberKnightLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

vm_delete

Destructive

Preview a VM deletion's blast radius, then confirm to permanently remove the VM, its disks, and snapshots.

Instructions

[WRITE] Delete a VM and its disks and snapshots (irreversible).

Without confirm=True this only previews: it returns blast_radius (identity, host, disks, total size, snapshot count, blockers) and destroys nothing. Show that to the user and get their explicit decision. Do not set confirm=True on your own because the user said "delete" earlier: they have not seen what it destroys yet.

To delete, call again with confirm=True and acknowledge_blast_radius set to the preview's acknowledge_with object, unchanged. The VM is re-measured first; if it changed (another snapshot, a different VM under the same name), nothing is deleted and you must preview again.

Refused outright: a powered-on or suspended VM (power it off with vm_power_off first), a VM whose disks or identity cannot be read, and a name that matches more than one VM. Use vm_set_ttl instead when the VM should only expire later.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNovCenter/ESXi target name from config.
confirmNoFalse (default) previews; True deletes, with the acknowledgement.
vm_nameYesExact name of the VM to delete.
acknowledge_blast_radiusNoThe preview's acknowledge_with object.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.12.10

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, and the description goes well beyond them. It explains the two-phase preview/delete behavior, the re-measurement safety check before deletion, the irreversible destruction of disks and snapshots, and the exact refusal conditions.

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 dense but every sentence carries operational weight, and the most critical facts (irreversibility, two-phase behavior, user consent) are front-loaded. The structure moves from purpose to preview requirement to deletion protocol to refusals and alternatives without waste.

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 having no output schema, the description explains what the preview returns (blast_radius with identity, host, disks, size, snapshot count, blockers, and acknowledge_with) and covers all refusals and safety checks. An agent has everything needed to call this tool safely and 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?

Schema coverage is 100%, and the description adds significant meaning beyond the schema: confirm=False previews while confirm=True deletes, acknowledge_blast_radius must be the preview's acknowledge_with object unchanged, and the toolbox is re-measured before deletion. This makes the two-phase contract unambiguous.

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 states a specific verb and resource: delete a VM, including its disks and snapshots, and notes irreversibility. It also distinguishes this tool from related relatives by directing the agent to vm_set_ttl for expiration-only cases and vm_power_off for powered-on VMs.

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?

Usage is explicitly gated: preview first with confirm=False, show the blast radius to the user, then delete with confirm=True and the unchanged acknowledge_blast_radius. It gives clear when-not-to-use conditions (powered-on/suspended VMs, unreadable disks, ambiguous names) and names the alternative tool for each relevant case.

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