Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Cve Search

cve_search

Search the NVD for recent CVEs by keyword and filter by minimum CVSS score to identify vulnerabilities that match specific risk criteria.

Instructions

Search the NVD for recent CVEs by keyword, filtered by minimum CVSS score.

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": {
      "keyword": "<keyword>"
    },
    "name": "cve_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYes
min_cvssNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it discloses the data source (NVD), that results are 'recent', and that min_cvss filters results. It omits rate-limit behavior, the definition of 'recent', and pagination/limit semantics, leaving meaningful gaps for a search tool.

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?

A single front-loaded sentence with no wasted words; the scope (NVD, recent, keyword) and filter (min CVSS) are stated immediately. It is appropriately sized, though its brevity edges into under-specification rather than pure conciseness.

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?

An output schema exists, so return values need not be explained, and the description supplies the source, keyword, and CVSS filter. However, without annotations, undefined 'recent', undocumented limit behavior, and no differentiation from cve_lookup leave the definition only minimally complete.

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 description coverage is 0%, so the description must compensate. It explains keyword and min_cvss only superficially and never mentions the limit parameter, its default of 20, or whether a maximum 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?

States a specific verb and resource: search the NVD for recent CVEs by keyword, with a CVSS filter. This is clear on its own, but it never distinguishes itself from the sibling cve_lookup, which an agent could easily confuse with this tool.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus cve_lookup, whether the NVD API key is required, or what 'recent' means. The only implied usage is keyword-based CVE search, and alternatives are not mentioned.

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