Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Assess vulnerability risk

cybersecurity-intelligence_risk-assess

Produce a consolidated vulnerability risk assessment for multiple packages, combining OSV, CISA KEV, EPSS, and NVD data. Price $0.15 USDC. POST /api/v1/cybersecurity-intelligence/risk/assess. Unpaid calls return 402 and do not run.

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": {
      "packages": "<packages>"
    },
    "name": "cybersecurity-intelligence_risk-assess"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden, and it does add real value by disclosing a fixed price ($0.15 USDC) and that unpaid calls return 402 without executing — that payment/auth behavior is not in the schema. It still omits whether the operation is read-only, what happens if some packages fail to resolve, rate limits, and what the consolidated result contains, so significant gaps remain.

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?

Four short sentences, front-loaded with the purpose, then data sources, then price, then payment failure mode — the important constraints come early with no filler. The raw endpoint path (POST /api/v1/...) is the one element of questionable value to an agent.

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?

There is no output schema and no annotations, so the description is the only source of truth, and it covers purpose, sourcing, and payment but not the shape of the returned assessment or per-package failure handling. For a paid, multi-input aggregation tool this is adequate but leaves an agent unable to predict the response.

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% and the single parameter is a nested array of objects requiring ecosystem, package, and version, none of which are documented. The description says only 'multiple packages' and does not explain accepted ecosystem strings, version formats, or that the list is capped at 10 entries, so it fails to compensate for the schema gap.

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 opens with a specific verb and resource — 'Produce a consolidated vulnerability risk assessment for multiple packages' — and names the four data sources (OSV, CISA KEV, EPSS, NVD) that make up the result. An agent can tell this is a multi-package aggregate, distinct from a single-package check, though it never names the sibling (package-batch-check) it most overlaps with.

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?

The phrase 'for multiple packages' implies this is the bulk variant versus a single-package tool, which is useful implied routing. However, there is no explicit when-to-use or when-not guidance, no statement of prerequisites, and no pointer to an alternative for one-off lookups or for dependency-wide audits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources