Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Clear Job Cache

clear_job_cache
Destructive

Clears the local backup cache for a Veeam Agent backup policy when the repository is unreachable; verify cached restore points are uploaded before running.

Instructions

Clear the backup cache of a Veeam Agent backup policy (the local cache agents write to while the repository is unreachable). Make sure cached restore points were uploaded first.

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": {
      "job_id": "<job_id>"
    },
    "name": "clear_job_cache"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.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, but the description adds substantive value the annotations cannot: it explains that the cache exists for offline operation and warns that un-uploaded restore points could be lost. It stops short of describing irreversibility or the rollback path.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences: the destructive action first, the safety precondition second. No filler, no restatement of the title, and the most decision-relevant information is front-loaded.

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?

Output schema exists, so return values need no explanation, and the destructive nature plus precondition are covered. However, for a destructive tool with an undocumented confirm_token the description leaves a real invocation gap that the agent must resolve from the schema alone.

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% for both parameters, and the description never mentions job_id or confirm_token — including the confirmation token, which materially affects how the call must be made. The description adds no meaning beyond the bare schema types.

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 concrete verb and resource ('Clear the backup cache of a Veeam Agent backup policy') and disambiguates the vague term 'cache' with a parenthetical definition of what is being removed. An agent knows exactly what will be affected, though nothing routes it away from any near-neighbor operation.

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?

Provides a real precondition — 'Make sure cached restore points were uploaded first' — which tells the agent when invoking would be unsafe. It does not state when to prefer this over other cleanup/reconfiguration tools or what to do if the precondition fails, so guidance is implied at best.

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