Skip to main content
Glama
Sign In
cve-cache-mcp

cve-cache-mcp

by weiseer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

find_for_package

Retrieve all CVEs affecting a specific package, with optional ecosystem filtering for npm, PyPI, Cargo, Maven, or Go.

Instructions

All CVEs affecting a package. Optionally filter by ecosystem.

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

Input Schema

NameRequiredDescriptionDefault
ecosystemNonpm/pypi/cargo/maven/go
package_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. It states the tool returns all CVEs but does not disclose pagination, ordering, coverage (e.g., only latest vs historical), or any restrictions. It provides minimal behavioral context.

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?

The description consists of two short, front-loaded sentences with no unnecessary words. Every word adds value.

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 tool with 2 parameters and no output schema, the description is adequate but lacks details on return format, ordering, or pagination. An agent may need more context to fully leverage the tool.

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?

The schema coverage is 50% (only ecosystem has a description). The description mentions package_name and ecosystem as optional filter, adding context about optionality but not providing detailed semantics for package_name. It partly compensates for the missing schema description.

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 clearly states that the tool lists all CVEs for a given package with optional ecosystem filtering. The verb 'find' and resource 'CVEs affecting a package' are specific, and the sibling tools (e.g., lookup_cve for individual CVEs, list_recent_critical for recent critical ones) provide distinction.

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 description implies when to use (for package-based CVE lookup) but does not explicitly state when not to use or mention alternatives. The sibling names give context, but the description itself lacks clear usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools