Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Start Quick Backup

start_quick_backup

Start an on-demand incremental backup for a single machine already protected by a Veeam backup job, using that job's settings to add a restore point to its chain.

Instructions

Quick Backup: an on-demand incremental of one machine that is already protected by a backup job.

object is the inventory object exactly as VBR returns it: for vsphere/cloud_director a VmwareObjectModel (platform, hostName, name, type: VirtualMachine, objectId) from vbr-mcp browse_inventory; for hyperv a HyperVObjectModel; for agent an AgentObjectModel (id, name, type, protectionGroupId, platform: Agent). The machine must have a backup in a job; VBR uses that job's settings and adds a restore point to its chain. Returns a session.

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": {
      "platform": "<platform>",
      "object": "<object>"
    },
    "name": "start_quick_backup"
  }
}

Input Schema

NameRequiredDescriptionDefault
objectYes
platformYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description adds real context beyond them: the operation is incremental, inherits job settings, appends a restore point to an existing chain, and returns a session. What it omits is the role of confirm_token, which is notable for a mutation tool but not contradictory to the annotations.

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 definition is front-loaded with the one-line summary, then expands only the parameter that needs it. The per-platform enumeration is dense but each clause adds distinct information; no sentence is pure filler.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nested-object mutation tool with a 0%-covered schema, the description supplies the platform-specific object shapes, the preconditions, and the return type. The remaining hole is the undocumented confirm_token flow, plus no hint about failure behavior when the machine lacks a job.

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 load; it does this well for `object`, spelling out the exact model per platform and even pointing to browse_inventory as the source. However, `confirm_token` is never mentioned at all, leaving one of three parameters entirely undocumented anywhere.

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?

The first sentence gives a precise verb and resource: an on-demand incremental backup of a single already-protected machine. It also implicitly distinguishes itself from full job runs by noting it reuses the existing job's settings, so an agent can tell it apart from restoration or configuration siblings.

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?

The definition states a hard precondition ('The machine must have a backup in a job') and clarifies the effect (VBR uses that job's settings and appends a restore point), which tells the agent when this tool is appropriate. It stops short of naming an alternative or exclusion, so the choice against other start_* tools is only implied.

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