Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Get Session Result

get_session_result
Read-onlyIdempotent

Retrieves the state and result of a Veeam Backup & Replication session, optionally polling until it stops and returning logs when warnings or failures occur.

Instructions

State and result of a VBR session - the asynchronous run started by almost every action tool.

With wait_seconds, polls every 5 s until the session reaches Stopped or the time is up. When the session stopped with a Warning or Failed result (or include_logs and it is still running), the session log records are included so the reason is visible.

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": {
      "session_id": "<session_id>"
    },
    "name": "get_session_result"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYes
include_logsNo
wait_secondsNoPoll until the session stops, up to this.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the readOnly/idempotent annotations: a 5-second poll cadence, the terminal state ('Stopped'), and the conditional rule that log records are included on Warning/Failed or when include_logs is set while still running. Does not cover what happens without wait_seconds on a still-running session, so not a 5.

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

Conciseness4/5

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

Front-loaded with the outcome statement, then conditional behavior in two compact sentences. The clause '(or `include_logs` and it is still running)' is slightly tangled but still parses; no filler.

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

Completeness4/5

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

Output schema exists, so return values needn't be described, and the description is complete enough for correct invocation. The one gap is the default/immediate-return behavior when wait_seconds is 0 and the session is still running.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% (only wait_seconds is documented in-schema), so the description must compensate. It does: it explains that wait_seconds polls until Stopped or timeout, and that include_logs governs whether log records are returned — meaningful semantics the schema does not carry.

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

Purpose5/5

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

States a specific verb+resource ('state and result of a VBR session') and explicitly anchors it to the asynchronous run started by action tools, which distinguishes it from stop_session/stop_automation_session siblings that act on sessions rather than report them.

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

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly implies the when: after invoking any action tool that returns a session_id, call this to resolve the outcome. No explicit exclusions or named alternatives, but the context ('almost every action tool') gives an agent enough to place it in a workflow.

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