Skip to main content
Glama
badchars

supply-chain-mcp-server

by badchars

nvd_cve

Retrieve complete CVE details from the NVD database for any known vulnerability identifier. Obtain full descriptions, severity scores, and references to assess impact.

Instructions

Fetch full CVE details from NVD (NIST National Vulnerability Database) by CVE ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cve_idYesCVE identifier (e.g. CVE-2023-44487)
Behavior2/5

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

No annotations provided. Description does not disclose rate limits, authentication requirements, return format, or any behavioral traits beyond 'fetch full details'. Lacks transparency for external API.

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?

Single sentence, front-loaded with action and resource. Every word is necessary and informative.

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?

Tool is simple with one parameter and no output schema. Description covers basic purpose but does not specify return structure or potential errors. Adequate but minimal.

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 already describes the parameter. Description does not add new meaning beyond restating 'by CVE ID'. Expected baseline score for high coverage.

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?

Clearly states the action (fetch), resource (full CVE details), source (NVD), and input method (by CVE ID). Distinguishes from siblings like nvd_search and nvd_recent.

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?

Implied use case (have a CVE ID, fetch its details). No explicit when-to-use, when-not-to-use, or alternative tools mentioned. Sibling tools like nvd_search or nvd_recent are not referenced.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/badchars/supply-chain-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server