Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Stop Session

stop_session
Destructive

Terminate a running restore, recovery, rescan, or other Veeam session by ID. Completed work is not rolled back, so partial VM or file output may remain.

Instructions

Stop a running session of any type: a restore, Instant Recovery, rescan, health check, SureBackup, malware scan, move/copy, etc. (for a backup job run, vbr-mcp stop_job gives graceful-stop control).

What is already done is not rolled back; a stopped restore can leave a partially restored VM or files behind.

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

Input Schema

NameRequiredDescriptionDefault
session_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this destructive and non-idempotent, so the description's real contribution is the consequence model: work already completed is not rolled back and a stopped restore may leave a partially restored VM or files behind. That is valuable context an agent cannot get from hints. It does not explain the confirm_token requirement or any permission prerequisites, which keeps it from 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.

Conciseness5/5

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

Two tight sentences: scope and sibling routing first, irreversible-consequence warning second. No filler, and the most decision-relevant information is front-loaded.

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?

For a destructive single-target tool with an output schema and full annotation coverage, the description supplies the missing consequence semantics that structured fields cannot express. The remaining gap is the undocumented confirm_token workflow, which matters for actually invoking a destructive call correctly.

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% for two parameters, so the description carries the full burden and provides nothing: neither session_id (how to obtain a valid session UUID) nor confirm_token (that it is a confirmation gate for a destructive action) is explained. The agent must guess the purpose of the second parameter entirely.

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?

The description opens with a specific verb and resource ('Stop a running session') and then enumerates the session types covered (restore, Instant Recovery, rescan, health check, SureBackup, malware scan, move/copy). It also explicitly excludes backup job runs and points to the correct tool for those, so the agent can separate this from job-stop operations without opening the schema.

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?

It gives a clear condition for use (any running session type) and names an alternative with the condition that selects it ('for a backup job run, vbr-mcp `stop_job` gives graceful-stop control'). It stops short of disambiguating other stop-shaped siblings such as stop_task or stop_automation_session, so guidance is strong but not exhaustive.

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