Skip to main content
Glama

SBOM Dependency CVE & US CISA Known Exploited Vulnerability MCP

Batch Audit Up to 15 SBOM Dependencies ($0.05 USDC via x402)

batch_sbom_cve_audit_x402
Read-onlyIdempotent

Audits up to 15 dependency specs in parallel against OSV.dev + CISA KEV ($0.05 USDC on Base via x402).

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

Input Schema

NameRequiredDescriptionDefault
packagesYesItems like npm:lodash@4.17.19

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds genuinely new behavioral context: a monetary cost ($0.05 USDC on Base via x402) and the upstream data sources, both of which matter before invoking. It stops short of explaining the x402 payment handshake or what happens when more than 15 items are supplied.

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?

One sentence, front-loaded with the action and the limit, with cost and data sources packed into the same clause. No filler and nothing that could be cut without losing information.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only audit with no output schema, the description covers what it does, the size limit, and the price. The remaining gap is operational: how the x402 payment is attached and how over-limit batches or payment failures behave.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter at 100% schema coverage, the baseline is 3; the description earns one more by stating the 15-item cap, a constraint the schema does not encode. The expected item format (npm:lodash@4.17.19) is already in the schema, so no additional credit is due there.

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 (audits) and resource (dependency specs / SBOM entries) with concrete scope: batch, up to 15, in parallel, against OSV.dev + CISA KEV. An agent can distinguish it from the singular audit_package_cve_and_cisa_kev sibling by the batch/parallel framing, though the description never names that alternative explicitly.

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 'up to 15' bound implies this is the bulk path and that larger sets need multiple calls, but there is no explicit when-to-use or when-not-to-use guidance and no routing to the single-package sibling. Usage must be inferred from the batch wording.

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.