Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Check package vulnerabilities

cybersecurity-intelligence_package-check

Check one package and version for vulnerabilities using OSV, enriched with CISA KEV, EPSS, and NVD data. Price $0.03 USDC. POST /api/v1/cybersecurity-intelligence/package/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": {
      "ecosystem": "<ecosystem>",
      "package": "<package>",
      "version": "<version>"
    },
    "name": "cybersecurity-intelligence_package-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageYes
versionYes
ecosystemYes

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, the description carries the full burden and does well: it discloses the price ($0.03 USDC), the payment behavior (unpaid calls return 402 and do not run), and which vulnerability feeds enrich the result. It stops short of describing failure modes for unknown packages/versions or result shape, which keeps it below 5.

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, front-loaded sentences: purpose and data sources first, then cost, endpoint, and payment failure behavior. Little waste, though the raw endpoint path adds less value to an agent than parameter guidance would have.

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?

For a straightforward lookup tool with no output schema, the description covers what data is used and the payment gate, which is adequate. It is incomplete on the two things an agent most needs to call it correctly: valid ecosystem values and version string format.

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% across three required parameters. The description restates "package and version" but never addresses ecosystem (which likely governs valid package identifiers) or version format expectations such as exact-version matching. The critical semantics are left 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?

States a specific verb and resource ("Check one package and version for vulnerabilities") and names the underlying data sources (OSV, CISA KEV, EPSS, NVD). The emphasis on "one package" implicitly contrasts with the batch sibling, though no sibling is named outright, so differentiation is inferential rather than explicit.

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 singular scope ("one package") implies single-package lookups and hints that bulk work belongs elsewhere, but no alternative tool is named and no when-not-to-use condition is given. Guidance is implied, not stated.

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