Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Delete Backup Object

delete_backup_object
Destructive

Delete one machine's restore points from a Veeam backup ("Delete from disk" for a single VM or computer). This action is irreversible; provide backup and object IDs.

Instructions

Delete one machine's restore points from a backup ("Delete from disk" for a single VM/computer).

object_id is the backup object id from vbr-mcp get_backup_details(include objects). 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>",
      "object_id": "<object_id>"
    },
    "name": "delete_backup_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes
object_idYes
include_gfsNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is largely covered. The description still adds value by specifying "Delete from disk" (actual data removal, not a catalog-only removal) and "Irreversible" (no recycle-bin undo), which destructiveHint alone does not guarantee.

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: scope and the UI analogue first, then the id provenance, then the irreversibility flag. Nothing is redundant and the warning lands where it will be read.

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

Completeness3/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 values need not be described, and annotations carry the safety profile. However, for an irreversible mutation with a `confirm_token` parameter, leaving that token's purpose and the `include_gfs` flag undocumented is a meaningful omission.

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 description coverage is 0% across four parameters, and the description explains only `object_id`, via a cross-tool provenance pointer. `backup_id`, `include_gfs`, and especially `confirm_token` are left completely undefined, so the description compensates for only a quarter of the gap.

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 names a specific verb and resource and pins the scope: "Delete one machine's restore points from a backup," with the UI analogue "Delete from disk" for a single VM/computer. That scope statement lets an agent distinguish it from whole-backup or object-level siblings like delete_backup and delete_object.

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?

It supplies a real prerequisite — where `object_id` comes from (`get_backup_details(include objects)`) — which is actionable context. But it never states when to choose this over a broader delete, nor any preconditions such as the backup needing to be idle or the object detached, so usage is only implied.

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