Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Manage Malware Exclusions

manage_malware_exclusions
Destructive

Create, update, or delete malware-detection exclusions for backup objects; server confirmation is required because exclusions weaken detection.

Instructions

Create/update (upsert, with exclusions - a list of MalwareDetectionCommonSpec, see describe_model) or delete (with exclusion_ids) malware-detection exclusions for backup objects. Exclusions weaken detection, so both are 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": {
      "action": "<action>"
    },
    "name": "manage_malware_exclusions"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
exclusionsNo
confirm_tokenNo
exclusion_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the risk profile is known. The description adds real value by warning that exclusions weaken detection and that the server confirms both operations, which explains the confirm_token parameter. It stops short of saying what a delete removes or whether existing exclusions are replaced on upsert.

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 dense sentences with no filler; the action-to-parameter mapping comes first and the risk/confirmation caveat follows. Every clause carries information an agent needs.

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 not be described, and the destructive/confirmation behavior is covered. The remaining gap is minor: it never states whether upsert also requires a confirm_token or how existing exclusions are affected.

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, and it does for three of four parameters: it names the action enum values, describes `exclusions` as a list of MalwareDetectionCommonSpec with a pointer to describe_model, and ties `exclusion_ids` to delete. `confirm_token` is only implied by 'confirmed by the server' and never named.

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 specific verbs (create/update via `upsert`, `delete`) and the exact resource (malware-detection exclusions for backup objects), and maps each action to its distinguishing parameter. An agent can tell the two modes apart 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 Guidelines4/5

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

Gives clear conditional guidance for choosing between the two actions (`upsert` with `exclusions` vs `delete` with `exclusion_ids`) and points to describe_model for the spec shape. It does not address when to prefer this tool over adjacent ones like set_backup_file_malware_state, but the action routing is explicit.

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