Skip to main content
Glama
URBackup MCP
by MarkPhsd

urbackup_restore_image

Starts a disk image restore for a specified backup and returns the restore token and auth key the client needs. Requires confirmation to proceed.

Instructions

Start an image (disk) restore. Returns a restore token and authkey that the restore client needs.

Args: backup_id: Image backup ID (from image_backups in urbackup_list_backups). confirm: Must be true to actually start the restore.

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": {
      "backup_id": "<backup_id>"
    },
    "name": "urbackup_restore_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNo
backup_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that confirm gates the action and that a restore token and authkey are returned, which is helpful, but it does not warn that an image restore is destructive, may overwrite disk data, or require the restore client to be online.

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 description is short and front-loaded: the core action and return values come first, followed by parameter notes. Every sentence contributes useful information, though the Args section could be slightly tighter.

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?

The output schema already covers return values, so the description need not explain them. Still, for a destructive restore operation with no annotations, it should say more about prerequisites, side effects, and when to use it instead of urbackup_restore_files.

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%, so the description must compensate. It does so for both parameters: backup_id is sourced from image_backups in urbackup_list_backups, and confirm is explained as the flag that must be true to actually start the restore.

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 states a specific verb and resource: 'Start an image (disk) restore.' This clearly distinguishes it from a generic restore and implies it is not the same as the sibling urbackup_restore_files, though it does not name that sibling explicitly.

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?

It gives useful prerequisite guidance by pointing to urbackup_list_backups and the image_backups field, and it explains that confirm must be true to proceed. However, it does not explicitly say when to choose this tool over urbackup_restore_files or what conditions must hold before starting an image restore.

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