Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Delete Backup

delete_backup
Destructive

Deletes an entire backup and all restore points from disk, with options to include GFS points or remove only from VBR configuration. Use when you need irreversible backup removal.

Instructions

Delete a whole backup (all restore points of every machine in it) from disk.

include_gfs=True also deletes GFS (weekly/monthly/yearly) restore points - without it they are kept. from_configuration_only=True removes the backup only from the VBR configuration (fromDB) and leaves the files on the repository (they can be imported again). Immutable restore points cannot be deleted before their immutability expires; VBR then reports an error. Irreversible.

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": {
      "backup_id": "<backup_id>"
    },
    "name": "delete_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes
include_gfsNo
confirm_tokenNo
from_configuration_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the destructiveHint/readOnlyHint annotations, the description discloses exactly what is destroyed (every restore point of every machine), the GFS retention side effect of omitting include_gfs, the config-only variant that preserves files, the immutability error condition, and closes with 'Irreversible.' That is substantive behavioral context an agent needs before a destructive call.

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?

Front-loaded with the core action, then one clause per option, then constraints, then a one-word severity marker. No filler sentences; each line maps to a distinct decision the caller must make.

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?

An output schema exists, so return-value explanation is not required, and the destructive profile is fully covered. The remaining gap is the unexplained confirm_token, which could cause a failed or refused call on a high-risk operation.

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?

With 0% schema description coverage the description must carry parameter meaning, and it does explain include_gfs and from_configuration_only precisely. However, confirm_token — a parameter on a destructive operation — is never mentioned in either schema or description, and backup_id semantics are left implicit, so compensation is incomplete.

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 opening line gives a specific verb and resource plus the exact scope: 'Delete a whole backup (all restore points of every machine in it) from disk.' The scoping phrase distinguishes it from single-object deletion siblings such as delete_backup_object without naming them.

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?

It clearly states when to set include_gfs (to also remove GFS points) and from_configuration_only (to remove only from VBR config so files can be re-imported), and calls out the immutability precondition that blocks deletion. It does not explicitly route the agent to alternatives like mark_backup_objects_clean or delete_backup_object, so the when-not guidance is partial.

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