Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_restore_files

Restore selected files or directories from a specific backup to an online client, with an optional glob filter and confirmation required before execution.

Instructions

Restore files from a backup to the client (client must be online).

Args: client_id: Client ID. backup_id: Backup ID to restore from. path: Path of the file or directory inside the backup to restore. file_filter: Optional glob filter for files (e.g. "*.docx"). confirm: Must be true to actually perform the restore.

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>",
      "path": "<path>"
    },
    "name": "urbackup_restore_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
confirmNo
backup_idYes
client_idYes
file_filterNo

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 does disclose two valuable behaviors: the online-client prerequisite and the confirm gate that prevents an accidental restore. It omits the most consequential traits for a write operation — whether existing files on the client are overwritten, whether the restore is reversible, and whether it runs asynchronously (a urbackup_progress tool exists).

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?

The one-sentence summary front-loads the action and the online-client constraint, then the Args block maps cleanly to the five parameters. Slight redundancy in restating parameter names as their own glosses, but nothing is wasted.

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?

Output schema exists, so return values need no explanation, and required-vs-optional is clear from the schema. For a destructive restore operation with zero annotations, though, the description should state the overwrite behavior and whether the call blocks until completion — both are missing.

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 supply meaning, and it does name all five parameters including the glob example for file_filter and the "must be true" semantics of confirm. But client_id and backup_id are restated nearly tautologically ("Client ID", "Backup ID"), giving no hint about where to obtain those values or what a full-path restore of a directory implies.

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 ("Restore files from a backup to the client") plus a key precondition (client must be online). It implicitly separates itself from urbackup_restore_image and urbackup_browse_backup_files by scoping to files, but never names or contrasts an alternative explicitly.

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 parenthetical "client must be online" and the requirement that confirm be true give real usage context, and the file_filter example hints at narrowing a restore. However, it never says when to prefer file restore over image restore or that browsing (urbackup_browse_backup_files) is the way to discover backup_id/path first.

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