Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Reboot Recovery Appliances

reboot_recovery_appliances

Reboot Veeam Agent recovery appliances by ID, or all appliances when no IDs are supplied, to clear stuck states and restore availability.

Instructions

Reboot Veeam Agent recovery appliances (one by id, or all when appliance_ids is omitted).

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

Input Schema

NameRequiredDescriptionDefault
appliance_idsNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, and the description adds the important bulk-scope behavior. However, it says nothing about the `confirm_token` gate, which is the key behavioral detail for an operation that can reboot an entire fleet at once.

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?

A single front-loaded sentence with no filler; the default scope behavior is placed where it is most useful. Very tight, though it leaves no room for the missing confirmation semantics.

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

Completeness3/5

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

An output schema exists so return values need not be described, and the targeting behavior is well covered. For a fleet-wide mutation, the unexplained `confirm_token` and absent permission/authorization context leave a meaningful gap.

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%, so the description must carry parameter meaning. It does explain `appliance_ids` (omit to target everything) but leaves `confirm_token`, the safety-critical parameter, completely undefined in both schema and description.

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 states a specific verb and resource ('Reboot Veeam Agent recovery appliances') and clarifies scope ('one by id, or all'). No sibling tool shares this operation, so an agent can distinguish it without opening the schema, though it does not explicitly name a contrasting sibling.

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

Usage Guidelines3/5

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

It gives one useful usage rule: omitting `appliance_ids` reboots all appliances. It offers no when-not guidance, no prerequisites or permission requirements, and no warning that the all-appliances path is a bulk disruptive action.

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