Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

delete_snapshot

Destructive

Deletes a Proxmox VE guest snapshot by host, VMID, and snapshot name, with a required reason recorded for approval and logging.

Instructions

Delete a snapshot.

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": {
      "host": "<host>",
      "vmid": "<vmid>",
      "snapshot": "<snapshot>",
      "reason": "<reason>"
    },
    "name": "delete_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
vmidYesThe guest's ID (VMID).
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.
snapshotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered structurally. The description adds nothing beyond that—no statement of irreversibility, no note that the 'reason' surfaces in an approval dialog, no confirmation behavior. No contradiction, but no added value either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short, front-loaded sentence with no filler. It is technically concise but the brevity is under-specification rather than efficiency, leaving the agent with nothing actionable beyond the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation with four required parameters and no output schema; the description should convey irreversibility, the approval flow implied by 'reason', and preconditions. None of that is present, making it inadequate for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, with both 'host' and 'reason' well documented in the schema and 'snapshot' left undocumented. The description contributes no parameter meaning at all, so it fails to compensate for the uncovered 'snapshot' field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description restates the tool name ('Delete a snapshot') without adding specificity. It never distinguishes the resource from siblings like delete_backup or rollback_snapshot, so an agent gets no more than it could infer from the name alone.

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

Usage Guidelines1/5

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

There is no guidance on when to use this versus rollback_snapshot (which may remove snapshots too) or take_snapshot. No prerequisites, no exclusions, no alternatives are named.

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