Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Create Recovery Media

create_recovery_media

Creates Veeam Recovery Media as a bare-metal recovery ISO for an agent backup object, enabling system recovery from that backup.

Instructions

Create Veeam Recovery Media (bare-metal recovery ISO) for an agent backup object.

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_object_id": "<backup_object_id>"
    },
    "name": "create_recovery_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNoOptional body; see describe_endpoint.
confirm_tokenNo
backup_object_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/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 operation, so the safety profile is covered. The description adds that the output is a bare-metal recovery ISO, but says nothing about side effects, how long media generation takes, whether prior media is overwritten, or why a confirm_token parameter exists.

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?

A single tight sentence with the artifact clarification front-loaded alongside the action. Nothing extraneous, though it is arguably too short for the complexity involved.

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 non-read-only tool with an unexplained confirm_token and an untyped 'spec' body, the description leaves the agent without enough to invoke it safely and 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 only 33%; backup_object_id is implied by 'agent backup object', but confirm_token and the opaque 'spec' body are not explained at all, leaving the description unable to compensate for the undocumented parameters.

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 (create Veeam Recovery Media) and disambiguates what the artifact is with the parenthetical 'bare-metal recovery ISO', plus the scoping target 'agent backup object'. It is clearly distinct from generic creation siblings like create_object.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, no prerequisites (e.g., that the backup object must be an agent-based workload), and no mention of whether approval via confirm_token is expected before calling.

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