Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_download_file_url

Creates a session-scoped download URL for a single file stored in a backup, helping you retrieve or restore that file from the backup server.

Instructions

Get a session-scoped URL to download a single file from a backup.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
backup_idYes
client_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the entire behavioral burden. It does disclose one genuinely useful trait — the URL is session-scoped, i.e. it expires — but says nothing about required permissions, whether the file is streamed or served, or what happens when the path does not exist in that 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?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity is partly the cause of the missing parameter and usage detail rather than purely a virtue.

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

Completeness2/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 the tool takes three required, fully undocumented parameters and has no annotations, leaving the description far short of what an agent needs to call it correctly.

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%: all three parameters (client_id, backup_id, path) carry only bare titles. The description hints that path refers to a file inside a backup but never states whether it is relative to the backup root, absolute, or how to obtain backup_id from urbackup_list_backups.

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?

The description pairs a specific verb ("Get") with a specific artifact ("a session-scoped URL to download a single file from a backup"). The phrase "a single file" implicitly separates it from the zip-download sibling, though it never names that sibling, so the differentiation is only partial.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to prefer this over urbackup_download_zip_url, urbackup_restore_files, or urbackup_browse_backup_files, and no prerequisites such as needing an existing backup or a valid client/backup pair. Usage is only inferable from the word "download".

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