Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Batch check package vulnerabilities

cybersecurity-intelligence_package-batch-check

Check multiple packages and versions for vulnerabilities using OSV batch query, enriched with CISA KEV, EPSS, and NVD data. Price $0.10 USDC. POST /api/v1/cybersecurity-intelligence/package/batch-check. 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_package-batch-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
packagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations at all, the description carries real weight and does add behavior beyond the name: it states the price ($0.10 USDC) and that unpaid calls return 402 without running. That payment/failure contract is valuable and not derivable from the schema. It stops short of describing error behavior for malformed ecosystems, rate limits, or what the response payload contains.

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?

Three short sentences, front-loaded with what the tool does, then cost and endpoint, then the payment failure mode. No filler; the endpoint path is arguably redundant but cheap.

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?

No output schema and no annotations, so the description should carry more: it never says what a result looks like (per-package vulnerability lists? severity? KEV/EPSS enrichment placement) or how enrichment fields appear. Combined with a wholly undocumented nested input schema, an agent can call it but cannot anticipate 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 coverage is 0% — the nested package/version/ecosystem objects have no descriptions, no enum for ecosystem, and the maxItems of 20 is only in the schema. The description contributes nothing about parameter meaning, accepted ecosystem identifiers, or version format, so the agent gets no guidance beyond field names.

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?

States a specific verb and resource ('Check multiple packages and versions for vulnerabilities') plus the data sources used (OSV batch query, CISA KEV, EPSS, NVD), which distinguishes it clearly from a coverage-focused tool like dependency-tree or lockfile-audit. It does not explicitly contrast with the single-package 'package-check' sibling, relying on 'multiple'/'batch' to imply the difference.

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 word 'multiple' implies this is the choice when checking several packages at once rather than one, but there is no explicit when-to-use/when-not-to-use statement and no named alternative. An agent must infer the routing decision from the name and the plural phrasing.

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