Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Security Analyzer

security_analyzer
Destructive

Start security and compliance scans, suppress confirmed best-practice findings with a note, reset finding statuses, and manage scan schedules.

Instructions

Security & Compliance Analyzer: start a scan; suppress one best-practice finding (with a note - it stops being reported, so it is confirmed); reset one finding's status or reset_all. Schedule: update_settings(area='security_analyzer_schedule').

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": "security_analyzer"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
actionYes
confirm_tokenNo
best_practice_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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 safety profile is known before reading. The description adds the genuinely useful fact that suppressing permanently stops reporting a finding, which is a real consequence beyond the annotations. It is silent, however, on the `confirm_token` mechanism that a destructive tool presumably requires, and on whether `start` is synchronous or long-running.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Everything sits in one semicolon-chained sentence with backticked enum tokens, which keeps it short and front-loads the tool's name. But the compression crosses into under-specification: the reader must reverse-engineer which action each parameter belongs to, and the sentence repeats the title verbatim before saying anything useful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 explained. For a destructive, four-parameter tool with zero schema description coverage, though, the description leaves the confirmation flow, the meaning of `best_practice_id`, and the effects of `reset_all` unaddressed; the scheduling pointer is the only piece of operational guidance provided.

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 must carry all parameter meaning and it does not. `note` and `best_practice_id` are hinted at obliquely ('one best-practice finding (with a `note`)'), but `confirm_token` is never mentioned at all despite being the gate on a destructive operation, and no parameter is tied to its intended action.

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 names concrete operations: start a scan, suppress a best-practice finding, reset one finding or reset_all. It also refers scheduling out to `update_settings(area='security_analyzer_schedule')`, so an agent can distinguish scope from that sibling. It stops short of five because 'start a scan' never says what is scanned or what the scan covers.

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?

Usage is only implied by mapping each enum value to a one-word gloss. The one real qualification given is behavioral, not a when-to-use rule: `suppress` takes a `note` and 'stops being reported, so it is confirmed'. Nothing says when suppress is preferable to reset, or what the preconditions for `start` are.

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