Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Set Backup File Malware State

set_backup_file_malware_state
Destructive

Mark a backup file as Clean or Infected to control restore access: infected blocks normal restores, while clean lifts the restriction after server confirmation.

Instructions

Mark one backup file (restore point file) as Clean or Infected for malware detection.

Marking infected blocks normal restores from it (secure restore only); marking clean lifts that, so it is confirmed by the server.

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": {
      "backup_id": "<backup_id>",
      "backup_file_id": "<backup_file_id>",
      "state": "<state>"
    },
    "name": "set_backup_file_malware_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYes
backup_idYes
confirm_tokenNo
backup_file_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds real value on top: it explains the operational consequence (infected blocks normal restores, secure restore only; clean lifts the block). The gap is the unexplained confirmation flow — the trailing 'so it is confirmed by the server' is ambiguous and never connects to the confirm_token parameter.

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?

Two front-loaded sentences with the mutation and its consequence stated immediately. The final clause 'so it is confirmed by the server' is garbled and slightly undermines an otherwise clean structure.

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 no explanation, but for a destructive, non-idempotent mutation with zero schema parameter documentation, the missing confirmation-token semantics and id disambiguation leave a real completeness 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% across 4 parameters, so the description must carry the burden. It only echoes the state values; it never explains the difference between backup_id and backup_file_id or when confirm_token is required, leaving the caller to guess on a destructive operation.

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 and resource with explicit scope: 'Mark one backup file (restore point file) as Clean or Infected.' The word 'one' implicitly distinguishes it from bulk operations like mark_backup_objects_clean among the siblings, so an agent can tell what this does 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 Guidelines3/5

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

Usage is implied through the stated effect (blocking normal restores), which tells an agent why it would call this, but there is no explicit when-to-use versus alternatives, no prerequisite/permission guidance, and no mention of when the bulk sibling should be preferred instead.

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