Veeam VBR v13 MCP Server

GetAllAutomationSessions

Retrieve all automation import and export sessions from Veeam Backup & Replication v13 to monitor data transfer operations and track session status.

Instructions

Get all automation import/export sessions.

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

Input Schema

Name	Required	Description	Default
`skip`	No
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

TDQS

C2.1/5.0

Behavior1/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 but fails to do so. It doesn't indicate whether this is a read-only operation, if it requires authentication, what the return format is, or if there are rate limits. This is inadequate for a tool that likely returns a list of sessions.

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, making it easy to parse quickly, though this conciseness comes at the cost of detail.

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 complexity of retrieving sessions, lack of annotations, 0% schema coverage, and no output schema, the description is severely incomplete. It doesn't cover behavior, parameters, return values, or usage context, making it inadequate for effective tool invocation.

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 for its two parameters ('skip' and 'limit'), and the description adds no information about them. It doesn't explain what these parameters do, their expected values, or how they affect the session retrieval, leaving them completely undocumented.

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

Purpose3/5

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

The description 'Get all automation import/export sessions' clearly states the verb ('Get') and resource ('automation import/export sessions'), making the purpose understandable. However, it doesn't distinguish this tool from similar sibling tools like 'GetAllSessions' or 'GetAutomationSession', leaving the scope vague regarding what makes these sessions specific to automation import/export.

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. It doesn't mention prerequisites, context for automation sessions, or compare it to sibling tools like 'GetAllSessions' or 'GetAutomationSession', 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