Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_start_backup

Starts on-demand incremental or full file/image backups for one or more specified clients, enabling targeted backup runs from the URBackup MCP server.

Instructions

Start a backup for one or more clients.

Args: client_ids: Client IDs (from urbackup_status). backup_type: One of incr_file, full_file, incr_image, full_image.

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_ids": "<client_ids>",
      "backup_type": "<backup_type>"
    },
    "name": "urbackup_start_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idsYes
backup_typeYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Start' strongly implies an asynchronous kickoff, yet the description never says whether the call blocks, returns a job reference, or whether the caller should poll urbackup_progress; it also omits prerequisites such as the client being online or a backup already running.

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 every line, including the Args block, contributes information. The docstring-style Args formatting is slightly mechanical but not wasteful.

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?

For a two-parameter mutation tool with no annotations, the description covers both parameters and their sourcing, and an output schema exists so return values need not be explained. What is missing is the operational context an agent needs — async behavior, success/failure semantics, and interaction with in-progress states.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the schema declares backup_type as a bare string with no enum, so the description's listing of the four allowed values (incr_file, full_file, incr_image, full_image) and the sourcing hint for client_ids add real meaning. It stops short of explaining the file-vs-image or incr-vs-full distinction.

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 plus resource ('Start a backup for one or more clients'), which clearly separates it from read-only siblings such as urbackup_status or urbackup_list_backups. It does not explicitly name a contrasting sibling, but the action is unambiguous.

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 '(from urbackup_status)' note implies a prerequisite workflow, which is useful implied usage guidance. However, there is no statement about when to pick this tool versus alternatives (e.g., stop/progress tools) or how to choose between incremental and full backups.

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