Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_delete_backup

Remove a specific backup for a client by supplying client and backup IDs; require confirmation and optionally delete immediately instead of marking it for deletion.

Instructions

Delete a backup. confirm=true required.

Args: client_id: Client ID. backup_id: Backup ID. delete_now: Delete immediately instead of marking for deletion.

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

Input Schema

NameRequiredDescriptionDefault
confirmNo
backup_idYes
client_idYes
delete_nowNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden for a destructive operation. It does disclose a genuinely valuable behavior: by default the backup is only marked for deletion, and delete_now forces immediate removal. It stops short of stating whether marking is reversible, whether permissions are required, or that immediate deletion is irreversible.

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?

A one-line purpose statement followed by a compact Args list; every line maps to a parameter and nothing is padded with prose. The format is easy to scan, though the Args block largely mirrors the schema titles.

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?

For a destructive, unannotated tool the definition is thin: reversibility, permission requirements, and the effect on dependent archives are unstated. An output schema exists so return values needn't be explained, and the confirm/delete_now semantics are present, which keeps this from being inadequate.

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 description coverage is 0%, so the description must compensate for all four parameters. It covers all of them, but client_id and backup_id are restated tautologically ("Client ID", "Backup ID"), and only delete_now receives real semantic explanation. It also conflicts with the schema, which lists confirm as optional with default false while the description calls confirm=true required.

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?

Opens with a specific verb+resource: "Delete a backup." That is unambiguous about what the tool does. It offers no differentiation from siblings such as urbackup_archive_backup or urbackup_unarchive_backup, so an agent must infer the boundary itself.

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 definition supplies a hard prerequisite ("confirm=true required"), which is useful gating information. However it never says when to prefer this over archiving or restoring a backup, nor when deletion should be avoided.

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