Skip to main content
Glama

SBOM Dependency CVE & US CISA Known Exploited Vulnerability MCP

Audit Software Package for OSV CVEs & CISA Exploited Vulnerabilities

audit_package_cve_and_cisa_kev
Read-onlyIdempotent

Audits an npm, PyPI, Go, Cargo, or Maven package version against OSV.dev and US CISA Known Exploited Vulnerabilities.

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": {
      "name": "<name>"
    },
    "name": "audit_package_cve_and_cisa_kev"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name (e.g. lodash, requests)
versionNoExact version string (e.g. 4.17.19)
ecosystemNonpm, PyPI, Go, crates.io, or Maven (default npm)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine context by naming the external sources being queried and the supported ecosystems, but it says nothing about latency/rate limits, whether a missing package returns empty versus an error, or what the result 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?

One dense sentence with the verb, supported ecosystems, and sources front-loaded; nothing is padding. It is arguably over-compressed, since trimming ecosystem names would not have cost clarity while return-value information would have bought more.

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, so the description bears the burden of describing the response, and it never mentions whether results include CVE IDs, severity, KEV status, or affected ranges. Annotations plus the schema cover safety and inputs, but for an audit tool the missing output characterization is a real gap.

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

Parameters3/5

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

Schema coverage is 100% and each of the three parameters is already documented with an example, so the baseline is 3. The description adds little parameter-level detail beyond reiterating the ecosystem list, and it says 'Cargo' where the schema enum-style text says 'crates.io', a minor terminology mismatch an agent must reconcile.

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) plus the resource (a package version) and names the two data sources (OSV.dev and CISA KEV), so the agent knows exactly what the call produces. It never explicitly contrasts itself with the batch/SBOM sibling, which keeps it from a 5.

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: naming a single package name/version suggests per-package auditing and the 'default npm' note clarifies the common case. There is no explicit when-to-use or when-not guidance, and no pointer to the batch_sbom_cve_audit_x402 sibling for multi-package scans.

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.