Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Manage Discovered Computers

manage_discovered_computers
Destructive

Manage discovered computers in a protection group: install or uninstall agents and CBT drivers, rescan, reboot, trust, prepare for recovery, or remove a computer.

Instructions

Act on computers a protection group discovered (ids from vbr-mcp get_protection_group_entities).

Additive actions run directly: install/upgrade agent, install CBT driver, rescan, trust, prepare for remote bare-metal recovery, recreate embedded recovery media. Confirmed by the server: uninstall agent / CBT driver / all components, reboot, remove (removes one computer from the group - pass exactly one id).

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": {
      "protection_group_id": "<protection_group_id>",
      "action": "<action>",
      "entity_ids": "<entity_ids>"
    },
    "name": "manage_discovered_computers"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
entity_idsYes
confirm_tokenNo
protection_group_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and non-idempotent, and the description reinforces this by grouping destructive operations under 'Confirmed by the server' and noting that remove drops one computer from the group. However, it never explains how confirmation is obtained, whether confirm_token is required for destructive actions, or that removal is scoped to the group rather than deleting the machine. With annotations covering the safety profile, this is useful but partial added context.

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 paragraphs that lead with the resource and then the additive/destructive split; every clause carries information. The fragment 'Confirmed by the server:' is terse to the point of ambiguity about the confirm_token mechanism.

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, but a 12-action destructive tool with zero schema coverage needs more: the confirm_token workflow and per-action preconditions are absent. An agent can pick an action but may not know how to satisfy the confirmation path.

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 full param burden, and it only partially succeeds: it clarifies action semantics and the one-id cardinality for remove on entity_ids. The confirm_token parameter is never named or explained (only implied by 'Confirmed by the server'), and protection_group_id is undocumented beyond its literal name.

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?

The description names the exact resource (computers discovered by a protection group) and enumerates the full action set, including edge semantics like 'remove' affecting a single computer. It also points to the sibling tool that supplies the ids, so it is distinguishable from surrounding management tools.

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?

It clearly splits actions into additive ones that run directly versus ones requiring server confirmation, which is real routing guidance for the action parameter, and tells the agent where entity ids come from. What's missing is any statement of when not to use this tool or which sibling handles adjacent cases.

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