Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Move Backup Objects To Job

move_backup_objects_to_job
Destructive

Move backup objects from one job to another so the target job continues their backup chains; omit object IDs to move all objects.

Instructions

Re-home machines' backups from one job's backup to another job (e.g. after moving VMs between jobs), so the target job continues their chains. Without backup_object_ids all objects of the backup move.

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_job_id": "<target_job_id>"
    },
    "name": "move_backup_objects_to_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
backup_idYes
confirm_tokenNo
target_job_idYes
backup_object_idsNo
move_associated_backup_copiesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description usefully adds the blast radius: omitting backup_object_ids moves every object of the backup. That is real value beyond annotations for a destructive operation. However, it says nothing about confirm_token (whether it is a confirmation requirement or dry-run guard), the effect on existing chains/copies, or reversibility.

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?

Two sentences, front-loaded with the operation and its purpose, with the default-scope caveat placed last where it is most needed. Every clause carries information; only the parenthetical example could be trimmed.

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

Completeness2/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 need not be described, but for a destructive five-parameter mutation with zero schema description coverage the description is too thin. It omits the confirm_token contract and the meaning of move_associated_backup_copies, which are exactly the details an agent needs before invoking an irreversible re-homing operation.

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 5 parameters, so the description must carry the burden, but it only clarifies backup_object_ids and only its default behavior. confirm_token and move_associated_backup_copies are left completely unexplained, and backup_id vs target_job_id semantics are only loosely implied by the narrative.

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+resource: re-home machines' backups from one job's backup to another job, so the target job continues their chains. That is concrete and distinguishable from generic backup movement. It does not explicitly contrast with the sibling 'move_backup', so an agent must infer which of the two applies.

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?

Provides an implied usage context ('e.g. after moving VMs between jobs'), which gives the agent a scenario for selecting this tool. It offers no when-not guidance, no prerequisites, and no named alternative for moving an entire backup rather than individual objects.

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