Skip to main content
Glama
Sign In
AIops-tools

xcpng-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

snapshot_delete

Destructive

Permanently deletes a VM snapshot by UUID. Preview with dry_run; prior state captured for audit, irreversible.

Instructions

[WRITE][risk=high] Delete a VM snapshot by uuid. IRREVERSIBLE.

Captures the snapshot's prior state (name / time / parent VM) for the audit
record; declares no undo.

Args:
    snapshot_id: Snapshot uuid (see snapshot_list).
    dry_run: If True, preview without deleting.
    target: Xen Orchestra target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
targetNo
dry_runNo
snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and non-idempotency, but the description adds material context beyond them: irreversibility, that no undo is registered, that prior state (name/time/parent VM) is captured for audit, and that dry_run allows a safe preview. This is unusually rich disclosure for a destructive tool.

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?

Front-loaded with impact tags and the core action, followed by a tightly structured Args block. The audit-record sentence is slightly wordier than needed but earns its place by disclosing audit behavior.

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 high-risk, non-idempotent write with no output schema, the description covers action, irreversibility, param meaning, and the dry_run escape hatch. It stops short of stating required permissions or the shape of the dry_run/deletion response, which would fully close the loop.

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 description coverage is 0%, so the description carries the full burden and does: snapshot_id is the snapshot uuid (with snapshot_list as source), dry_run is a non-destructive preview, and target is the Xen Orchestra target name from config with an explicit 'omit for default' default behavior.

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?

Specific verb+resource ('Delete a VM snapshot by uuid') with severity/type tags ([WRITE][risk=high]) and an explicit irreversibility claim. It also points to snapshot_list for obtaining the uuid, distinguishing it from sibling read/restore tools.

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

Usage Guidelines4/5

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

The IRREVERSIBLE warning plus dry_run preview and the 'declares no undo' statement give clear context for when this is appropriate, and snapshot_list is named for id lookup. However, it never explicitly contrasts with snapshot_revert/undo_apply, so the routing is implied rather than stated.

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