VMware-AIops

vm_delete

Destructive

Permanently delete a powered-off virtual machine. Removes the VM from vCenter or ESXi inventory.

Instructions

[WRITE] Delete a VM (irreversible). VM must be powered off.

Args: vm_name: VM to delete. Must be powered off. target: 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": "vm_delete"
  }
}

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

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds 'irreversible' and the power-off precondition, which are valuable behavioral traits 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 concise, with two sentences and a brief args list. It front-loads the purpose and is free of fluff, making it efficient for an AI agent to process.

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?

Given the tool's simplicity, the description covers the main purpose, preconditions, and parameters. It assumes the output schema handles return values, but omits potential error scenarios. Overall adequate for this context.

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?

With 0% schema description coverage, the description compensates by briefly explaining both parameters: 'vm_name: VM to delete. Must be powered off.' and 'target: vCenter/ESXi target name from config.' This adds meaning beyond the schema structure, though more detail on valid values could help.

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 it deletes a VM irreversibly, with a specific verb and resource. It distinguishes from sibling tools like vm_power_off or vm_clone by explicitly mentioning 'Delete' and 'irreversible'.

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

Usage Guidelines3/5

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

The description provides a precondition (VM must be powered off) but does not explicitly compare to alternatives or state when not to use. While it implies usage for permanent deletion, lack of direct comparison to siblings like vm_power_off or vm_create_snapshot limits guidance.

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