Skip to main content
Glama
Sign In
VMware-AIops

VMware-AIops

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

vm_rollback_plan

Destructive

Rollback executed steps of a failed VMware plan in reverse order, skipping irreversible actions with a warning.

Instructions

[WRITE] Rollback executed steps of a failed plan in reverse order.

Only call this after vm_apply_plan returns status='failed' and the user confirms they want to rollback. Irreversible steps (delete_vm, revert_snapshot, etc.) are skipped with a warning.

Args: plan_id: The plan ID of the failed plan. 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": {
      "plan_id": "<plan_id>"
    },
    "name": "vm_rollback_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetNo
plan_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.5.29
  2. Removedv1.5.28
  3. Addedv1.5.18

TDQS

A4.5/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations: it rolls back in reverse order, skips irreversible steps with warnings, and marks itself as [WRITE]. This complements the destructiveHint=true annotation effectively.

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 concise and front-loaded with [WRITE] and core purpose. The Args section is necessary given 0% schema coverage, but it could be integrated more cleanly. Still, no wasted sentences.

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 rollback tool, it covers when to use, what it does (reverse order, skip irreversible), and parameters. Missing return value details, but no output schema exists. Overall sufficient for the 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?

Schema coverage is 0%, but the description explains both parameters: plan_id is 'the plan ID of the failed plan', and target is 'Optional vCenter/ESXi target name from config'. This adds meaning beyond the schema titles.

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 specifies the action ('rollback'), the resource ('executed steps of a failed plan'), and the order ('reverse order'). It distinguishes from sibling tools like vm_apply_plan and vm_create_plan by being specifically for rollback after failure.

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?

Explicit guidance is provided: call only after vm_apply_plan returns status='failed' and user confirms. It also warns that irreversible steps are skipped with a warning, which helps the agent decide when to invoke.

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