Skip to main content
Glama

NS Pros MCP Gateway

nvd__search_cves

Search NVD for CVE vulnerabilities by product or component name. Returns CVE ID, description, severity, and CVSS score. Search terms are matched against CVE description text and EVERY word must appear, so pass the product name ("OpenSSL", "log4j", "nginx") optionally with a technical term ("buffer overflow"), not a plain-English question. Use when researching security threats or checking if a known vulnerability affects your systems.

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": {
      "query": "log4j"
    },
    "name": "nvd__search_cves"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (default 10, max 2000)
queryYesProduct, component or technical term to match against CVE descriptions, e.g. "OpenSSL" or "log4j deserialization". Every word must appear in a CVE's description, so question words ("latest critical vulnerabilities in ...") match nothing and are stripped automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does usefully disclose the matching mechanics (every word must appear, question words are stripped) and the shape of the result set, which is genuine behavioral context. It says nothing about result ordering, pagination beyond the limit cap, rate limits, or authentication needs, so gaps remain for a tool with zero annotation coverage.

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?

The key constraint — every word must appear, so pass keywords not questions — is front-loaded and concrete, and each sentence carries content. It is somewhat long with repeated example lists that duplicate the schema's matching prose, a minor redundancy rather than filler.

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 two-parameter search tool with no output schema, the description correctly compensates by naming the returned fields and explaining the matching rule. However, with no annotations and no return schema, it leaves ordering, truncation behavior when limit is exceeded, and error cases (no matches) unaddressed.

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 description coverage is 100%, so both parameters are already documented, including the default of 10 and max of 2000 for limit. The description's examples ("OpenSSL", "log4j", "nginx", plus an optional technical term) and the warning that plain-English questions match nothing reinforce intent but largely restate what the schema already says; baseline 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?

The description states a specific verb and resource ("Search NVD for CVE vulnerabilities by product or component name") and enumerates the return fields (CVE ID, description, severity, CVSS score), so the agent knows exactly what it retrieves. It does not name or distinguish itself from plausible siblings such as get_cve or recent_cves, leaving that differentiation to inference from sibling names.

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?

It gives a clear use context: "Use when researching security threats or checking if a known vulnerability affects your systems." There are no explicit exclusions or pointers to alternatives (e.g., use get_cve for a specific CVE ID, recent_cves for latest entries), which keeps it at a 4 rather than a 5.

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.