Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Run Backup Health Check

run_backup_health_check
Destructive

Run a storage-level CRC/consistency health check on selected backups or jobs; optionally repair corrupted blocks or mark broken restore points after confirmation.

Instructions

Run a storage-level health check (CRC/consistency) on backups, optionally repairing what it finds.

Give backup_ids and/or job_ids. repair=True rewrites corrupted blocks / marks broken points and is confirmed as destructive; repair_options is a HealthCheckRepairOptions object. Returns a session.

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

Input Schema

NameRequiredDescriptionDefault
repairNo
job_idsNo
backup_idsNo
confirm_tokenNo
repair_optionsNo

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 flag readOnlyHint=false and destructiveHint=true, and the description usefully adds what repair actually does (rewrites corrupted blocks, marks broken points) plus that it returns a session. However it is silent on whether repair requires a confirmation step and how that interacts with the destructive flag, which is the key operational detail an agent needs. Solid addition over annotations, but an important behavioral gap remains.

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?

Short, front-loaded, and paragraphed by concern: purpose, targeting, repair semantics. Sentences are dense with information rather than filler. Minor waste in restating 'repair=True ... is confirmed as destructive' in a way that is slightly ambiguous.

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 the description does not need to describe return values. But for a destructive, 5-parameter tool with zero schema description coverage, missing explanation of confirm_token and of repair_options contents leaves the agent under-informed about how to actually invoke a repair safely.

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?

With 0% schema coverage across five parameters, the description has to carry the load and only partly does. It explains that backup_ids/job_ids are selectors usable in combination, that repair is a boolean toggle with destructive effect, and that repair_options is a HealthCheckRepairOptions object, but it leaves repair_options opaque and never mentions confirm_token, whose role in authorizing destruction is critical. The parameters most consequential to safe invocation are the least documented.

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?

States a specific verb and resource: a storage-level CRC/consistency health check on backups, with an optional repair mode. That is distinct from the mutation siblings (delete_backup, move_backup) and from mark_backup_objects_clean. It never explicitly contrasts with those siblings, so it stops just short of a 5.

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?

Guidance is implied rather than stated: 'Give backup_ids and/or job_ids' tells the agent to target backups or jobs, and 'optionally repairing' implies a check-only vs repair mode. There is no explicit when-to-use or when-not-to-use framing, and nothing says whether a dry check should precede a repair run.

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