Skip to main content
Glama

Preview backup pruning

proxmox_preview_backup_prune
Read-only

Preview which backups would be kept or removed by retention rules without deleting anything; run the prune action with the same arguments to apply.

Instructions

Dry run of pruning a backup storage: shows which backups the retention rules (the storage's own, or retention) would keep and which they would remove. Nothing is deleted; run proxmox_prune_backups with the same arguments to apply.

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": {
      "storage": "<storage>"
    },
    "name": "proxmox_preview_backup_prune"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode to access the storage from (needed for node-local storages present on several nodes)
typeNoOnly VM or only container backups
vmidNoOnly this guest's backups
storageYesBackup storage to prune
retentionNoRetention to apply instead of the storage's configured prune-backups, e.g. {keep_last: 3}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds that no deletion occurs and that retention can come from the storage's own configuration or the explicit retention argument. It stops short of describing the shape of the preview output (per-backup list vs counts), which would have been useful given idempotentHint=false is unexplained.

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?

Two tight sentences, front-loaded with the dry-run scope and followed by the safety assurance and the apply pointer. No filler.

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 5-parameter tool with nested retention and no output schema, the description covers purpose, safety, and the effect of the retention override. The only gap is the exact form of the preview result, which the agent must infer from prose rather than a schema.

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

Parameters3/5

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

Schema coverage is 100% with per-parameter descriptions and a nested retention object, so the schema already carries the semantics. The description only reiterates that retention may be supplied instead of the storage's configured prune-backups, adding little beyond the schema's own wording.

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?

States a specific verb and resource ("Dry run of pruning a backup storage") plus the concrete effect (shows which backups the retention rules keep vs remove). The dry-run framing cleanly separates it from the apply tool without needing to open either schema.

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?

Explicitly says nothing is deleted and names the alternative: run proxmox_prune_backups with the same arguments to apply. This gives both the when-to-use (preview before committing) and the exact transition condition to the mutating sibling.

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