Veeam VBR v13 MCP Server

ImportCredentials

Add credential records to Veeam Backup & Replication v13 for secure authentication management in backup infrastructure.

Instructions

Import credentials records.

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

Input Schema

Name	Required	Description	Default
`body`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

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 whether this is a read or write operation, what permissions are required, if it's idempotent, what happens on failure, or any side effects. The single sentence lacks any transparency beyond the basic action.

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 extremely concise at just three words. While under-specified, it's not verbose or repetitive. Every word contributes to the core meaning without waste, making it front-loaded and efficient in structure.

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?

Given the tool has 1 parameter with 0% schema coverage, no annotations, no output schema, and involves nested objects (indicating complexity), the description is completely inadequate. It doesn't explain what 'credentials records' are, how to format the input, what the tool does beyond the verb, or what to expect as a result.

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?

Schema description coverage is 0%, and the description provides no information about the single parameter 'body'. It doesn't explain what the body should contain, its structure, format, or examples. The description fails to compensate for the complete lack of schema documentation.

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 'Import credentials records' restates the tool name with minimal elaboration. It specifies the verb 'Import' and resource 'credentials records', but lacks detail about what 'credentials records' are or how they differ from similar tools like 'ImportCloudCredentials' or 'CreateCreds'. This is borderline tautological with the name.

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 like 'ImportCloudCredentials', 'CreateCreds', or 'ChangePasswordForCreds'. The description offers no context, prerequisites, or exclusions, leaving the agent with no usage direction.

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

Deploy Server