Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Set Protection Group Enabled

set_protection_group_enabled
Destructive

Enable or disable a protection group to control discovery and agent deployment for its computers; disabling stops those operations for the group.

Instructions

Enable or disable a protection group. A disabled group stops discovery and agent deployment for its computers (disabling is 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": {
      "protection_group_id": "<protection_group_id>",
      "enabled": "<enabled>"
    },
    "name": "set_protection_group_enabled"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYes
confirm_tokenNo
protection_group_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare this as a non-readonly, destructive operation, and the description adds that disabling stops discovery and agent deployment for the group's computers. It also notes that disabling is confirmed by the server, but it does not describe enabling side effects, permissions, or other operational constraints beyond that.

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?

The definition is two sentences, front-loaded with the core action, and contains no wasted wording. The parenthetical adds useful confirmation behavior without disrupting structure.

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 and the annotations carry the safety profile, so the description does not need to explain return values or readonly status. However, it leaves a material gap around confirm_token and lacks usage guidance for a destructive state-changing operation.

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 three parameters, and the description only indirectly explains the enabled flag through 'enable or disable'. It does not explain protection_group_id or confirm_token, leaving the confirmation parameter entirely undocumented.

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?

The description states a specific verb pair and resource: enabling or disabling a protection group. It is clear what the tool acts on, but it does not explicitly differentiate this state toggle from nearby sibling operations such as rescan_protection_group.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance, no prerequisites, and no alternatives named. The only contextual clue is the effect of disabling, which helps explain consequences but not when an agent should choose this tool over another.

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