Skip to main content
Glama
AIops-tools

Nutanix AIops

by AIops-tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

snapshot_delete

Delete a Nutanix VM snapshot. Use dry run to preview the deletion and prevent errors.

Instructions

[WRITE][risk=high] Delete a VM snapshot. Destructive — pass dry_run=True to preview.

Tagged risk=high (audit tier 'review'); NUTANIX_AUDIT_APPROVED_BY /
NUTANIX_AUDIT_RATIONALE optionally annotate who/why. Captures the
snapshot's prior name on the audit trail.

Args:
    vm_ext_id: VM extId as returned by vm_list.
    snapshot_ext_id: Snapshot extId as returned by snapshot_list.
    dry_run: If True, return what WOULD be deleted without deleting.
    target: Prism Central target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
dry_runNo
vm_ext_idYes
snapshot_ext_idYes

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully carries the burden. It labels the tool as '[WRITE][risk=high]' and 'Destructive', explains audit trail capture, and mentions optional audit annotations. This thoroughly discloses behavior.

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 and well-structured, starting with the core action, then risk, then parameter details. No redundant sentences.

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?

No output schema exists, but the description covers all necessary aspects: purpose, risk, parameters, and audit trail. It is complete for a deletion tool.

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 0%, but the description explains each parameter: vm_ext_id from vm_list, snapshot_ext_id from snapshot_list, dry_run for preview, and target default behavior. This adds significant meaning beyond the schema.

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 starts with 'Delete a VM snapshot', a specific verb and resource. It distinguishes from sibling tools like snapshot_list, snapshot_create, and snapshot_restore.

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 description advises using dry_run=True to preview before actual deletion, providing clear usage guidance. It lacks explicit when-not-to-use instructions but clearly states the destructive nature.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/Nutanix-AIops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server