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

cve-cache-mcp

by weiseer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

lookup_cve

Retrieve comprehensive CVE information and associated NVD and GHSA references by supplying a CVE or GHSA ID. Get structured vulnerability records for security analysis.

Instructions

Full record for one CVE by ID. Cited NVD + GHSA URLs.

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

Input Schema

NameRequiredDescriptionDefault
cve_idYese.g. CVE-2024-12345 or GHSA-xxxx-xxxx-xxxx

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It mentions 'cited NVD + GHSA URLs' but does not detail other behavioral traits like read-only nature, rate limits, or response size. For a simple lookup, this is minimally adequate.

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 is one concise sentence (7 words) that front-loads the core purpose. Every word earns its place with no redundancy.

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

Completeness2/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 should explain return values. It only mentions 'Full record' and cited URLs, lacking specifics on what fields or structure the response contains. This is insufficient for a tool with no other docs.

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

Parameters2/5

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

Schema coverage is 100% and the description adds no additional meaning beyond what is already in the schema's parameter description. It merely repeats the ID format example, failing to add value.

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 the action: 'Full record for one CVE by ID.' It specifies the resource (CVE) and the scope (one by ID), distinguishing it from sibling tools like 'find_for_package' which searches by package.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies use when a specific CVE ID is known, but does not explicitly state when to avoid it or name alternatives. However, given the sibling tool names, context is clear.

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