Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_list_backups

Lists a client's file and image backups newest first, showing size, incremental status, archive state, and timestamps so you can inspect available restore points.

Instructions

List file and image backups for a client, newest first, with size, incremental flag, archive state and timestamps.

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

Input Schema

NameRequiredDescriptionDefault
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?

There are no annotations, so the description carries the full burden. It usefully discloses result ordering (newest first) and the returned attributes (size, incremental flag, archive state, timestamps), but says nothing about pagination, volume, permissions, or what happens when a client has no backups or an invalid client_id is supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and resource, and each clause (ordering, returned fields) contributes new information. There is no filler or repetition.

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

Completeness4/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 needn't be spelled out, and the description still previews them. For a single-parameter read tool this is close to complete; the main gap is the absence of guidance on the surrounding workflow and any filtering or archival behavior.

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 coverage is 0% and the sole parameter is undocumented in the schema. The phrase 'for a client' maps it to client_id, but the description does not say where a client_id comes from (e.g., urbackup_list_users or urbackup_status), nor whether archived backups are included by default.

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?

Specific verb plus resource ('List file and image backups') with an explicit scope ('for a client') and ordering ('newest first'). It clearly separates itself from mutation siblings like archive_backup or delete_backup, though it doesn't name a near-alternative such as browse_backup_files for per-file inspection.

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?

No when-to-use or when-not-to-use guidance is given; it states no prerequisites and does not direct the agent toward browse_backup_files, archive_backup, or restore tools. The usage is only implied by the verb 'List' and the required client_id.

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