Skip to main content
Glama
claude-proxmox-controller

claude-proxmox-controller

delete_backup

Destructive

Delete a non-protected Proxmox VE backup by host and volume ID. Provide a reason so the request can be approved and logged.

Instructions

Delete a backup (not a protected one).

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>",
      "volid": "<volid>",
      "reason": "<reason>"
    },
    "name": "delete_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesThe host's id, from list_hosts.
volidYes
reasonYesWhy you are doing this, in a sentence. The user sees it in the approval window and in the log.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/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 one useful behavioral fact, that protected backups are rejected, but does not state what happens to data on deletion, whether the operation is reversible, or how the approval flow behaves beyond what the reason parameter's schema already says.

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 a single tight sentence with no wasted words and the key constraint front-loaded. Brevity is appropriate, though it shades into under-specification for a destructive tool.

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

Completeness2/5

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

This is a destructive, three-required-parameter mutation with an undocumented volid and no output schema, yet the description is a seven-word sentence. For a high-stakes irreversible operation, the definition should at minimum explain volid and confirm the deletion scope, which it does not.

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 only 67%, and the single uncovered parameter is volid, whose meaning and format (datastore/volume identifier, expected syntax) are not explained anywhere in the description or schema. The description compensates for none of that gap; only the reason parameter's purpose is documented, and that already lives in the schema.

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

Purpose4/5

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

States a specific verb and resource ("Delete a backup") with a scope constraint added parenthetically ("not a protected one"). An agent immediately knows what the tool does, but the definition offers nothing to distinguish it from siblings such as delete_snapshot or delete_backup_job.

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 parenthetical implies a precondition (protected backups cannot be deleted), which is implied when-to-use guidance. However, there is no explicit guidance on when to use this instead of delete_backup_job, delete_snapshot, or restore_backup, and no statement of prerequisites such as the meaning of host.

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