Skip to main content
Glama

List known vulnerabilities of a package version

vulns
Read-only

Known vulnerabilities of one package version in the OSV database: npm, PyPI, crates.io, Go or Maven. Each advisory has its id, CVE aliases, summary, severity, fixed versions and a link. The count is the full number; up to 20 are listed. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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>",
      "name": "<name>",
      "version": "<version>"
    },
    "name": "vulns"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name
versionYesExact version, e.g. 4.17.20
ecosystemYesnpm, PyPI, crates.io, Go or Maven

Output Schema

NameRequiredDescriptionDefault
nameNo
noteNo
countNo
sourceNo
versionNo
checkedAtNo
ecosystemNo
vulnerabilitiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations cover read-only and open-world behavior, but the description adds context they cannot: results are truncated to 20 while the reported count is the full total, and each advisory carries id, CVE aliases, summary, severity and fixed versions. It also discloses the cost model ($0.002 per successful call via x402, failures uncharged), which is critical for an agent deciding whether to invoke it.

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?

Three sentences, front-loaded with what is retrieved, followed by the return contents and then the price. Nothing is redundant, and the truncation and billing facts are placed where an agent will read them before committing.

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?

For a three-required-parameter lookup with full schema coverage and an output schema, the definition covers scope, result shape, truncation limit and payment requirements. There is nothing an agent needs in order to call it correctly that 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 the property descriptions already define name, version and ecosystem, including the exact-version example. The description restates the ecosystem set and the one-version constraint but adds no format or validation detail beyond the schema, so the baseline of 3 applies.

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?

"Known vulnerabilities of one package version in the OSV database" names a specific resource and scope, and the ecosystem list bounds it precisely. It is not explicitly contrasted with the sibling package or package_search tools, so an agent must infer that this tool returns advisories rather than package metadata.

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 implied by the phrase "one package version" and the enumerated ecosystems, which signals that an exact version is mandatory and outside the list the tool will not serve. There is no explicit when-to-use/when-not guidance and no named alternative for looking up package metadata or searching by name.

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