Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Clone Job

clone_job

Clones a Veeam Backup & Replication job into a new copy with a derived name, letting you rename, adjust settings, and check its schedule before first run.

Instructions

Clone a job. VBR creates the copy under a derived name; rename or adjust it afterwards with update_object(kind='job', ...) and check its schedule before it first runs.

Supported job types: VSphereBackup, HyperVBackup, CloudDirectorBackup, BackupCopy, WindowsAgentBackup, LinuxAgentBackup. Returns the new job's model.

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": {
      "job_id": "<job_id>"
    },
    "name": "clone_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare a non-destructive write, and the description adds genuinely new behavior: VBR assigns a derived name rather than one you supply, the returned value is the new job's model, and the clone may auto-run on an inherited schedule unless reviewed. It does not explain what `confirm_token` gates or whether the clone is asynchronous, leaving a moderate gap.

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?

Three short sentences, front-loaded with the operation and followed by the type list and return value; every sentence carries information. The inline code formatting of the sibling call is slightly awkward 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?

An output schema exists, so the return value need not be belabored, and the type whitelist plus post-clone workflow are covered. However, for a mutation tool with an unexplained confirmation parameter and no note on permissions or async behavior, the definition is only adequate.

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% for both parameters, and the description never explains `job_id` (presumably constraining to the listed job types) or what `confirm_token` is for or when it is required. With zero schema-level documentation, the description had a compensating job to do and did not do it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Clone a job') and immediately scopes it by listing the six supported job types, so an agent knows whether this tool applies to a given job. It also names the sibling that handles post-clone edits (`update_object(kind='job', ...)`), which separates it from the update path.

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 clear operational context: the clone lands under a derived name, must be renamed/adjusted via update_object, and its schedule should be checked before it first runs. It lacks an explicit statement of when NOT to clone (e.g., versus create_object) and says nothing about permissions or prerequisites, but the usage context is strong.

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