Veeam VBR v13 MCP Server

EnableScaleOutExtentMaintenanceMode

Activate maintenance mode on a Scale-Out Backup Repository extent to perform maintenance tasks without disrupting backup operations.

Instructions

Enable maintenance mode on a SOBR extent.

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": {
      "id": "<id>"
    },
    "name": "EnableScaleOutExtentMaintenanceMode"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`body`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this requires special permissions, if it's reversible, what maintenance mode entails, potential impacts on operations, or any rate limits/side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence with zero wasted words. It's appropriately sized for the tool's apparent complexity and gets straight to the point without unnecessary elaboration.

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?

For a mutation tool with no annotations, 0% schema coverage, no output schema, and 2 parameters (one being a nested object), the description is inadequate. It doesn't explain what maintenance mode does, what parameters are needed, what happens after enabling it, or any error conditions.

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% with 2 parameters (id and body), and the description provides no information about either parameter. It doesn't explain what 'id' refers to (extent ID?), what the 'body' object should contain, or any required fields beyond what the minimal schema indicates.

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 ('Enable maintenance mode') and target resource ('on a SOBR extent'), providing a specific verb+resource combination. However, it doesn't differentiate from its sibling tool 'DisableScaleOutExtentMaintenanceMode' beyond the opposite action, missing explicit comparison.

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 guidance is provided on when to use this tool versus alternatives or prerequisites. The description lacks context about why or when maintenance mode should be enabled, and doesn't reference the sibling disable tool or other related tools.

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

Deploy Server