Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Start Encryption Analysis

start_encryption_analysis

Run an encryption analysis for a malware event to check whether backup data was encrypted, such as by ransomware, by providing the event ID.

Instructions

Run an encryption analysis for a malware event (checks whether data in the backup was encrypted, e.g. by ransomware). Event ids: vbr-mcp list_malware_events.

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": {
      "event_id": "<event_id>"
    },
    "name": "start_encryption_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
event_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations declare readOnlyHint=false, yet the text frames the tool as an 'analysis', which reads as passive inspection; nothing discloses what state is changed, whether the run is asynchronous, or how the job is tracked. The `confirm_token` parameter is not mentioned at all, so the agent gets no signal that a confirmation handshake may be involved.

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 tight sentences, front-loaded with the action and followed by the id source; no redundant restatement of the name. Slightly terse given the unaddressed confirmation parameter.

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 spelled out. However, for a non-read-only tool with an undocumented `confirm_token`, the definition leaves an agent without enough to invoke it safely and correctly on the first attempt.

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

Parameters3/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 burden. It does add real meaning for `event_id` (where to obtain one, and implicitly its format), but leaves `confirm_token` entirely unexplained — its null default and required usage are invisible to the agent.

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?

Names a specific verb and resource ('Run an encryption analysis for a malware event') and explains what it actually checks (whether backup data was encrypted, e.g. by ransomware). That scope cleanly separates it from the password-related encryption siblings, though no sibling is named explicitly.

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?

The description points the agent at `list_malware_events` as the source of event ids, which is genuine prerequisite guidance. It gives no when-not condition and does not contrast with `verify_encryption_password` or other encryption tools an agent might confuse it with.

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