security-framework-mcp

by zer0-kr

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_cve_detail

Read-onlyIdempotent

Retrieve comprehensive details for any CVE from the live NVD database.

Instructions

Fetch detailed information for a specific CVE from the live NVD database.

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

Input Schema

Name	Required	Description	Default
`cve_id`	Yes	CVE ID, e.g. 'CVE-2024-1234'

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering key behavioral aspects. The description adds 'from the live NVD database' indicating real-time data, but does not disclose error handling or rate limits. With annotations, the description provides minimal incremental transparency.

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 is a single sentence with no unnecessary words, efficiently conveying the tool's 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 an output schema exists, the description need not detail return values. It covers the essentials: fetching detailed info on a specific CVE from the live database. Minor omission: no mention of error behavior for invalid CVE IDs, but otherwise complete for its complexity.

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?

The input schema has 100% coverage, describing cve_id with pattern and example. The description does not add additional meaning beyond the schema, so baseline 3 is appropriate.

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 'Fetch detailed information for a specific CVE from the live NVD database.' It specifies the action (fetch), the resource (detailed info on a CVE), and the source (live NVD), distinguishing it from sibling tools like search_cve or get_cwe.

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?

The description implies usage for fetching details on a known CVE ID but does not explicitly state when not to use it or name alternatives like search_cve for searching. Usage context is implied but not clarified.

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