Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_progress

Monitor running backup and restore jobs with live progress, transfer speed, and ETA, and optionally review recent completed activities on the backup server.

Instructions

Show running backup/restore processes with progress, speed, ETA, and (optionally) the most recent completed activities.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "urbackup_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_last_activitiesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the returned information (progress, speed, ETA, recent completions), but says nothing about behavior when no process is running, permissions required, or whether 'last activities' is bounded/limited in size.

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 primary purpose, with the optional scope appended last. No filler or redundancy.

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?

A simple read-only query with one optional boolean and an existing output schema, which the description need not duplicate. What remains missing (empty-state behavior, activity limit) is minor for this complexity.

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% for the single parameter, but the description compensates partially by tying '(optionally) the most recent completed activities' to include_last_activities, conveying that it is a toggle for extra return data. It does not state the default (true in schema) or how many activities are included.

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 gives a specific verb ('Show') and a well-defined resource ('running backup/restore processes'), plus the exact fields returned (progress, speed, ETA). This is clearly distinguishable from a generic status tool, though it never names the sibling it complements (e.g. urbackup_status).

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?

Usage is only implied: an agent can infer this is for inspecting in-flight jobs rather than completed ones or client configuration. There is no explicit 'use this when X, use urbackup_status/list_backups when Y' routing, and no stated preconditions.

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