Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_download_zip_url

Generate a session-scoped URL to download a specific backup directory as a ZIP archive for restore or export.

Instructions

Get a session-scoped URL to download a directory from a backup as a zip.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
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.1/5.0
Behavior3/5

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

With no annotations, the description must carry the load; it does disclose two genuinely useful traits — the result is a URL rather than file bytes, and the URL is session-scoped (i.e. temporary). It omits anything on expiry duration, auth requirements, and whether server-side zip generation is triggered or slow for large directories.

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 wasted words. Its brevity is efficient, though it leaves nothing to address the parameter and behavioral gaps.

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 no explanation, but the tool takes four parameters with zero schema documentation and has no annotations. For a tool that produces download URLs against a backup set, the definition is under-specified for correct invocation.

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%, so the description must compensate for four undocumented parameters, and it does not. client_id, backup_id, path, and especially file_filter (format? glob vs regex? optional with empty default) are left entirely unexplained.

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: obtain a session-scoped URL to download a backup directory as a zip. 'Directory ... as a zip' implicitly separates it from urbackup_download_file_url, though the sibling is never 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?

The 'directory ... as a zip' phrasing implies the use case (bulk/whole-folder retrieval) versus a single-file download, but no explicit when-to-use, when-not-to-use, or alternative is given.

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