Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_browse_backup_files

Browse files and directories inside a URBackup backup, with optional mounting for image backups. Use it to locate and inspect backed-up data before restoring.

Instructions

Browse files inside a backup.

Args: client_id: Client ID. backup_id: Backup ID (from urbackup_list_backups). For image backups use the ID as listed in image_backups. path: Directory path to browse ("" = root). mount_image: Mount the image backup first if needed.

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

Input Schema

NameRequiredDescriptionDefault
pathNo
backup_idYes
client_idYes
mount_imageNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. "Browse" implies a read, but it never states that the operation is non-destructive, and critically it does not disclose the side effects or cost of mount_image (resource use, privileges, whether the mount persists), which is the one behavior an agent could get wrong here.

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 purpose sentence is front-loaded and the args block is scannable with no filler. The Args section is slightly repetitive of the schema titles but stays short.

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 no explanation. Still, for a tool with a conditional mount side effect and no annotations, the definition leaves gaps around mount behavior, permission requirements, and whether path browsing is flat or recursive.

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, and it does cover all four parameters: client_id, backup_id with its provenance, path with the "" = root default, and mount_image. However, the semantics are thin ("Client ID.") and it does not explain path format or whether listing is recursive.

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?

"Browse files inside a backup" gives a specific verb and resource, and the args block clarifies it is a per-client, per-backup listing operation. It distinguishes itself from urbackup_list_backups by naming it as the source of backup_id, though it does not explicitly contrast with restore or download siblings.

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 provides context for the backup_id argument (image backups use the ID from image_backups) and describes when to set mount_image, which gives implied usage guidance. It never states when to choose this over urbackup_restore_files or urbackup_download_file_url, nor any prerequisites such as required user rights.

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