Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Mark Backup Objects Clean

mark_backup_objects_clean
Destructive

Mark backup objects as clean after a malware investigation, typically a false positive, so normal restores are allowed again. A reason is required and recorded in the audit log.

Instructions

Mark backup objects (machines) as clean after a malware investigation - typically a false positive.

mark_restore_points_clean also clears the Suspicious/Infected flags of their restore points, so normal restores are allowed again. exclude_from_detection stops future detection for them (a security exception - use with care). reason is mandatory here and is stored by VBR and in the audit log.

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": {
      "object_ids": "<object_ids>",
      "reason": "<reason>"
    },
    "name": "mark_backup_objects_clean"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYes
object_idsYes
confirm_tokenNo
note_for_exclusionNo
exclude_from_detectionNo
mark_restore_points_cleanNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds that `reason` is mandatory and is recorded by VBR and the audit log, which is real context beyond structured fields. It also discloses the differing side effects of the two boolean parameters. It stops short of covering the confirmation requirement implied by `confirm_token`.

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?

Front-loaded with purpose and alternatives, using backticked parameter names to tie prose to schema fields; no filler sentences. Minor deductions for the awkward mid-sentence line break and for spending the first sentence on a purpose already implied by the title.

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?

An output schema exists, so return values need no explanation, and the alternative-comparison plus audit note cover what an agent needs to decide and act. The one real hole is `confirm_token`: for a tool flagged destructive, an undocumented null default may gate execution, which the definition never mentions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 the load; it explains three of six parameters in useful depth (`reason` being mandatory and audited, `mark_restore_points_clean` clearing Suspicious/Infected flags on restore points, `exclude_from_detection` creating a detection exception). `confirm_token` and `note_for_exclusion` remain undefined, and `object_ids` is only implied by "objects (machines)".

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 ("Mark backup objects (machines) as clean") plus the situation that motivates it ("after a malware investigation - typically a false positive"). It also explicitly separates itself from `mark_restore_points_clean` and `exclude_from_detection`, so an agent can pick correctly without opening a sibling schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use context (post-investigation, false positives) and names two alternatives with the exact condition that selects each: restore-points cleaning re-enables normal restores, while exclusion suppresses future detection. It even flags exclusion as "a security exception - use with care," which is a genuine when-not-to-use warning.

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