Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_archive_backup

Marks a specified backup as archived so it is protected from deletion; requires client ID, backup ID, and explicit confirmation.

Instructions

Archive a backup (protected from deletion). confirm=true required.

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_archive_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
backup_idYes
client_idYes

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, the description carries the full burden. It usefully discloses the effect of the operation (the backup becomes protected from deletion) and implies a confirmation guard, but says nothing about required rights, reversibility via unarchive, or what happens when archiving an already-archived backup.

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?

Two short clauses, front-loaded with the verb and resource, with the deletion-protection effect and the confirmation requirement immediately after. No filler, though the terseness leaves no room for the missing behavioral context.

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 explained, but for an unannotated state-changing tool the definition is thin: permissions, reversibility, and failure modes for the two required IDs are all unaddressed.

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 should compensate. It does so only for 'confirm', and valuably so: it clarifies that the flag must be true despite the schema declaring default=false. The two required identifiers (client_id, backup_id) receive no added meaning.

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 ('Archive a backup') and adds the operational meaning of the state change in parentheses ('protected from deletion'). An agent can tell this is the counterpart to unarchive-style operations even though no sibling is named.

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?

Provides one concrete usage prerequisite ('confirm=true required'), which is a real gating condition, but gives no guidance on when to archive versus deleting or leaving a backup alone, and no exclusions or named alternatives.

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