Veeam VBR v13 MCP Server

InstantUnstructuredDataRecoveryMount

Mount file share backups for immediate access to unstructured data during recovery operations.

Instructions

Start Instant File Share Recovery - mount a file share backup.

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": {
      "body": "<body>"
    },
    "name": "InstantUnstructuredDataRecoveryMount"
  }
}

Input Schema

Name	Required	Description	Default
`body`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a recovery operation but lacks details on permissions, side effects (e.g., if it modifies data), rate limits, or expected outcomes. This is inadequate for a tool with potential destructive implications.

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 description is a single, efficient sentence that front-loads the key action. It avoids unnecessary words, though it could be slightly more structured (e.g., separating purpose from context).

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?

Given the complexity (recovery operation with nested parameters), lack of annotations, 0% schema coverage, and no output schema, the description is insufficient. It doesn't explain what 'mount' entails, the recovery process, or expected results, leaving critical gaps for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage and includes a nested object ('body') with unspecified properties. The description adds no information about parameters, failing to compensate for the schema's lack of documentation, leaving the agent with no guidance on what to provide.

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 clearly states the action ('mount') and resource ('file share backup'), making the purpose understandable. It distinguishes from sibling tools like 'InstantUnstructuredDataRecoveryUnmount' by specifying the mount action, though it doesn't explicitly differentiate from other mount tools like 'AzureInstantVMRecoveryMount'.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It mentions 'Start Instant File Share Recovery' but doesn't clarify the context or conditions for invoking it, leaving usage ambiguous.

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

Deploy Server