Skip to main content
Glama

NS Pros MCP Gateway

nvd__get_cve

Get full details for a specific CVE (e.g., "CVE-2021-44228"). Returns description, severity, CVSS score, affected products, and remediation info. Use when you need comprehensive vulnerability analysis.

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": {
      "cve_id": "CVE-2021-44228"
    },
    "name": "nvd__get_cve"
  }
}

Input Schema

NameRequiredDescriptionDefault
cve_idYesCVE identifier, e.g. "CVE-2021-44228"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose the returned fields (description, severity, CVSS score, affected products, remediation), which is genuinely useful, but says nothing about authentication, rate limits, or what happens for an unknown or malformed CVE ID.

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?

Three short sentences, front-loaded with the purpose and immediately followed by output contents and usage. No filler, though the final usage sentence is the weakest and could have carried more discriminating information.

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

Completeness4/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 usefully enumerates what comes back, which is the main completeness risk for a lookup tool. The remaining gap is error/edge-case behavior for invalid or unmatched CVE IDs, which is modest for a one-parameter read.

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?

There is a single parameter with 100% schema description coverage, so the baseline is 3. The description's inline example ("CVE-2021-44228") mirrors what the schema already provides and adds no new constraint or format guidance beyond it.

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?

The description names a specific verb and resource (get full details for a specific CVE) and gives a concrete identifier example, so the agent knows exactly what the tool fetches. It does not distinguish itself from the sibling nvd__recent_cves, leaving the lookup-vs-list boundary implicit.

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?

"Use when you need comprehensive vulnerability analysis" gives a usage context, but it is vague and offers no when-not guidance. With a sibling like nvd__recent_cves present, the definition never states that this tool is for a single known CVE ID rather than browsing recent vulnerabilities.

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.