Veeam VBR v13 MCP Server

GetAllCloudCreds

Retrieve all cloud credential records (AWS, Azure, GCP) from Veeam Backup & Replication for management and monitoring purposes.

Instructions

Get all cloud credentials records (AWS, Azure, GCP, etc.).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "GetAllCloudCreds"
  }
}

Input Schema

Name	Required	Description	Default
`skip`	No
`limit`	No
`nameFilter`	No
`typeFilter`	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?

No annotations are provided, so the description carries full burden. It states it 'gets' records (implying read-only), but doesn't disclose behavioral traits like whether it requires authentication, returns paginated results, has rate limits, or what format the output takes. The description is minimal and lacks essential operational context.

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 front-loaded with the core purpose and includes helpful examples (AWS, Azure, GCP). Every part of the sentence adds value.

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 tool with 4 parameters, 0% schema coverage, no annotations, and no output schema, the description is inadequate. It doesn't explain parameter usage, output format, or behavioral constraints. Given the complexity and lack of structured documentation, the description should provide more context to be complete.

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%, and the description provides no information about the four parameters (skip, limit, nameFilter, typeFilter). It doesn't explain what these parameters do, their expected values, or how they affect the results. The description fails to compensate for the lack of schema documentation.

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 verb ('Get') and resource ('all cloud credentials records') with examples of cloud providers (AWS, Azure, GCP). It distinguishes from other 'Get' tools by specifying the resource type, but doesn't explicitly differentiate from sibling tools like 'GetCloudCreds' (singular) or 'ExportCloudCredentials'.

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 like 'GetCloudCreds' (for a specific credential) or 'ExportCloudCredentials'. The description implies it retrieves all records, but doesn't specify use cases, prerequisites, or exclusions.

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

Deploy Server