Skip to main content
Glama
Sign In
CVE Search MCP Server

CVE Search MCP Server

by Arnabdaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

search_cve_by_id

Search for a specific CVE by its exact ID to retrieve detailed vulnerability information, including CVSS score and severity analysis.

Instructions

Search for a specific CVE by exact ID (e.g., CVE-2021-44228). Use when you have a CVE ID from code, docs, or security reports. Returns complete CVE details with CVSS score and severity analysis.

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": "search_cve_by_id"
  }
}

Input Schema

NameRequiredDescriptionDefault
cve_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so the description carries the full burden. It states the tool returns 'complete CVE details with CVSS score and severity analysis', describing output behavior. However, it does not explicitly mention read-only nature, authentication needs, or rate limits. The description adds some transparency but could be more comprehensive.

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 consists of three brief, focused sentences: what the tool does, when to use it, and what it returns. No unnecessary words, and each sentence serves a distinct purpose.

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?

Given the tool's simplicity (one parameter, no annotations, output schema exists), the description is mostly complete. It covers purpose, usage context, and return value highlights. The only missing element is error handling or edge cases, but for a basic lookup that is acceptable.

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 0%, meaning the description must compensate. The description provides an example format (e.g., CVE-2021-44228) and implies exact ID matching, which adds semantic value beyond the schema. However, it does not specify validation requirements or accepted patterns, leaving gaps.

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 'Search for a specific CVE by exact ID', using a specific verb and resource. It distinguishes from sibling tools like 'bulk_cve_lookup' and 'search_by_keyword' by emphasizing exact ID, making the tool's unique purpose unambiguous.

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?

Provides explicit when-to-use guidance: 'Use when you have a CVE ID from code, docs, or security reports.' It does not explicitly state when not to use or name alternatives, but the context is clear and helpful for an agent.

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