Skip to main content
Glama

Package Vulnerabilities - OSV.dev advisories

osv_vulns
Read-onlyIdempotent

Known vulnerabilities for an open-source package version from OSV.dev (GitHub advisories, PyPI, npm, Go, Maven, crates.io...): id, CVE aliases, summary, severity, fixed versions, references. Plus what plain OSV lacks: CISA KEV 'exploited in the wild' flag + date, FIRST EPSS exploit probability, exploited/most-likely first, and one verified upgrade version that fixes every listed vuln. ~1 s. Free: 25 calls/day per IP. Paid: $0.002 per call via x402 at https://radarbg.com/x402/osv-vulns.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "package": "lodash",
      "version": "4.17.15",
      "ecosystem": "npm"
    },
    "name": "osv_vulns"
  }
}

Input Schema

NameRequiredDescriptionDefault
purlNoOr a package URL, e.g. pkg:npm/lodash@4.17.15
packageNoPackage name, e.g. lodash
versionNoVersion, e.g. 4.17.15 (empty = all known)
maxItemsNoMax results
ecosystemNonpm, PyPI, Go, Maven, crates.io, RubyGems, NuGet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent, and the description layers substantial extra context on top: ~1 s latency, a concrete rate limit (25 calls/day per IP), paid pricing via x402, result ordering (exploited/most-likely first), and the enrichment guarantees (KEV date, EPSS, one verified all-fixing upgrade). This is exactly the behavioral detail an agent needs beyond structured fields.

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?

Content is front-loaded: purpose and returned fields come first, then differentiators, latency, and cost. The long parenthetical ecosystem list and pricing sentence are dense but each carries real information; only minor trimming is possible.

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

Completeness5/5

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

With no output schema, the description compensates by enumerating returned fields and the ordering rule, and it covers cost, rate limits, and latency. For a read-only lookup with a fully documented schema, nothing an agent needs to invoke it correctly is missing.

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%, so package, version, ecosystem, purl, and maxItems are already documented. The description reinforces the ecosystem scope and version semantics but adds no format or edge-case detail beyond what the schema states; baseline 3 applies when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (known vulnerabilities for an open-source package version), the data source (OSV.dev), the ecosystems covered, and enumerates the returned fields (id, CVE aliases, summary, severity, fixed versions, references). The differentiators versus plain OSV — KEV flag, EPSS probability, verified upgrade version — make it unmistakably distinct from sibling tools like security_scan or domain_security_report.

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 scope ('package version') implies when to use it, and the schema note 'empty = all known' hints at versionless queries. However, there is no explicit when-to-use/when-not guidance and no naming of an alternative tool for adjacent tasks (e.g., domain or host security). Usage is inferable but not spelled out.

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