Skip to main content
Glama
Sign In
Veeam VBR v13 MCP Server

Veeam VBR v13 MCP Server

by kid-boy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

SetupMountServer

Add a new mount server to Veeam Backup & Replication v13 infrastructure for backup and restore operations.

Instructions

Add a new mount server.

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": "SetupMountServer"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations provided, the description carries full burden but offers no behavioral details. It doesn't disclose if this is a mutating operation, what permissions are required, potential side effects, or error conditions. The vague 'Add' implies creation but lacks critical context for safe invocation.

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, efficient sentence with no wasted words. It's appropriately front-loaded, though its brevity contributes to underspecification rather than true conciseness.

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

Completeness1/5

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

For a tool with no annotations, 0% schema coverage, no output schema, and a nested parameter object, the description is completely inadequate. It fails to explain what a mount server is, what the 'body' parameter expects, or what the operation returns, leaving the agent with insufficient context.

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 with one required parameter 'body' as an open-ended object. The description provides no information about what properties 'body' should contain, their semantics, or examples, leaving parameters completely undocumented.

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

Purpose2/5

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

The description 'Add a new mount server' restates the tool name 'SetupMountServer' with minimal variation, making it tautological. It lacks specificity about what a 'mount server' is or what 'adding' entails, failing to distinguish it from sibling tools like 'CreateManagedServer' or 'UpdateMountServer'.

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

Usage Guidelines1/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. It doesn't mention prerequisites, dependencies, or context for adding a mount server, nor does it reference sibling tools like 'GetAllMountServers' or 'UpdateMountServer' for related operations.

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

Deploy Server

Other Tools