Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Copy Backups

copy_backups

Copies backups to another repository or folder while leaving the source backup unchanged.

Instructions

Copy backups to another repository (or, for machine backups, a folder) - the source stays as it is.

spec is the request body: for unstructured_data a CopyBackupSpec (see describe_model); for machines VBR does not publish the schema - typically backupIds and a target repository or folder. Check describe_endpoint('/api/v1/backups/machines/copyTo', 'POST').

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": {
      "spec": "<spec>"
    },
    "name": "copy_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNomachines
specYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark this as non-readonly and non-destructive; the description adds real value by confirming the source is preserved and by disclosing that VBR does not publish the `machines` spec schema. It omits any mention of required permissions, whether the destination must pre-exist, or what `confirm_token` guards.

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 key behavior and the non-destructive guarantee are front-loaded in one sentence, followed by the spec guidance. The backticked references are dense but purposeful; nothing is filler.

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 tool with a nested object parameter, 0% schema coverage, and an output schema, the description does a reasonable job by delegating to `describe_model`/`describe_endpoint`. It still leaves `confirm_token` and `kind` behavior unexplained, which is a meaningful gap on a mutating tool.

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%, so the description carries the burden and does explain `spec` as the request body, naming `CopyBackupSpec` for unstructured data and `backupIds` plus a target for machines. However, `kind` and especially `confirm_token` — likely a mutation guard — receive no explanation, and the spec is delegated to other tools rather than described.

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 and resource (copy backups to another repository or folder) and explicitly separates itself from a move by stating 'the source stays as it is.' It does not name a sibling tool, but the copy-vs-move distinction is unambiguous enough for selection.

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 context is implied by the non-destructive framing ('source stays as it is'), and it points to `describe_model` and `describe_endpoint` for building the spec. It gives no explicit when-not or named alternative, so an agent must infer that moving rather than copying is a different tool.

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