Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Rescan Protection Group

rescan_protection_group

Trigger an immediate rescan of a protection group to discover new computers and refresh agent state, returning a session for tracking.

Instructions

Rescan a protection group now: discover new computers and refresh agent state. Returns a session.

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>"
    },
    "name": "rescan_protection_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
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?

Annotations already declare this is a non-read-only, non-destructive, non-open-world operation. The description adds real value beyond that by stating 'Returns a session', which tells the agent the rescan is asynchronous and that results must be fetched separately. It stops short of disclosing duration, whether repeated calls are coalesced, or what the session state progression looks like.

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 short sentences, front-loaded with the action and its effects, followed by the return contract. Nothing is padded or repeated.

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?

The presence of an output schema means return values need not be described, and the annotations plus the session mention cover the safety and async profile. However, for a mutation-style trigger with an undocumented confirm_token and no stated interaction model with sibling rescan tools, the definition is adequate but incomplete.

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%, so the description carries the full burden of explaining the two parameters — and it explains neither. In particular, 'confirm_token' is a non-obvious safety parameter with a null default, and the description gives no hint about when or why an agent must supply it.

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?

Uses a specific verb and resource ('Rescan a protection group now') and adds concrete effects ('discover new computers and refresh agent state'), so the agent knows exactly what the operation accomplishes. It does not distinguish itself from similar rescan siblings, but the stated effects are clear enough to stand on their own.

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?

The word 'now' hints that this triggers immediate execution rather than a scheduled scan, but there is no explicit when-to-use guidance, no prerequisites, and no exclusions. With multiple rescan_* siblings in the catalog, the description leaves the choice between them entirely to inference.

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