Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Rescan Replicas

rescan_replicas

Rescan Veeam Backup & Replication replicas to refresh their state; omit replica IDs to update all replicas.

Instructions

Rescan replicas to refresh their state in VBR (all replicas when replica_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": "rescan_replicas"
  }
}

Input Schema

NameRequiredDescriptionDefault
replica_idsNo
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the agent knows this is a non-destructive, non-open-world operation; the description adds that the effect is a state refresh rather than a config change. However, it never explains the confirm_token parameter or any confirmation/permission requirement, which matters for a tool flagged as non-read-only.

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, and the key scoping condition is stated inline rather than buried. Nothing is wasted, though the brevity comes partly at the cost of the missing confirm_token explanation.

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 all-replicas default is covered. For a tool flagged as non-read-only with an unexplained confirm_token, the definition is still missing enough behavioral detail to be fully 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%, so the description carries the full burden for both parameters. It explains only replica_ids (omitted means all replicas) and says nothing about confirm_token, leaving half the parameters undocumented 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 pairs the specific verb "Rescan" with the resource "replicas" and states the effect (refresh their state in VBR), which lets an agent distinguish it from the rescan_inventory, rescan_managed_servers and rescan_protection_group siblings by resource alone. It does not explicitly name any sibling as an alternative, so it stops short of full differentiation.

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?

There is no guidance on when to choose this over the other rescan_* or failover/failback tools, and no stated prerequisites or when-not-to-use conditions. The only conditional given is the parameter default (all replicas when replica_ids is omitted), which is parameter behavior rather than usage guidance.

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