Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Move Backup

move_backup
Destructive

Moves a backup chain to another repository and re-points its job to the target. Runs as a long move session, so jobs using that backup cannot run until it completes.

Instructions

Move a backup (whole chain) to another repository; the job is re-pointed to the target.

Runs as a move session and can take long; jobs using the backup cannot run meanwhile. If it stops halfway, manage_move_copy_session decides between retry, forget and undo.

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

Input Schema

NameRequiredDescriptionDefault
backup_idYes
confirm_tokenNo
target_repository_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds material context they don't carry: the whole chain moves, the job is re-pointed, the operation is long-running and session-based, and dependent jobs are blocked during the move. It doesn't mention permission requirements or exactly what happens to the source repository copy if the move fails outright.

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?

Two tight sentences, front-loaded with the action and its effect, then the operational caveats and the recovery path. No filler and no repetition of annotation data.

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?

An output schema exists, so return values needn't be described, and the failure/recovery story is covered. However, for a destructive move with zero schema coverage, the definition leaves the confirm_token requirement and any prerequisites unexplained, so an agent cannot fully determine how to invoke it correctly.

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% across three parameters, so the description must compensate and only partly does: 'a backup' and 'another repository' loosely map to backup_id and target_repository_id, but formats are left to the schema. The `confirm_token` parameter — presumably a safety gate on a destructive move — is never mentioned at all, which is a significant omission.

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 ('Move a backup (whole chain) to another repository') plus the side effect on the owning job ('the job is re-pointed to the target'). That differentiates it in substance from copy-style siblings, but no sibling is named explicitly, so it stops short of the top score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives real operational context for choosing and timing this call: it runs as a move session, can take long, and jobs using the backup cannot run meanwhile. It also routes the agent to `manage_move_copy_session` for retry/forget/undo when interrupted, though it never states when to prefer `copy_backups` or `move_backup_objects_to_job` instead.

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