Skip to main content
Glama
Sign In
NIST NVD MCP Server

NIST NVD MCP Server

by Cyreslab-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_cve_change_history

Retrieve change history for a specific CVE or filter by date range and event type to track vulnerability modifications.

Instructions

Get change history for a specific CVE or all changes within a date range

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cve_change_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
cveIdNoCVE identifier to get change history for
eventNameNoFilter by specific type of change event
changeEndDateNoEnd date for change range (ISO-8601 format, required if changeStartDate used)
resultsPerPageNoNumber of results per page (1-5000, default: 100)
changeStartDateNoStart date for change range (ISO-8601 format, max 120 day range)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether it is read-only, authentication requirements, or rate limits. It simply states the purpose without behavioral context.

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, clear sentence that front-loads the core purpose with no extraneous information.

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?

With 5 optional parameters and no output schema, the description is somewhat incomplete. It does not explain return format, pagination behavior, or date format expectations, though the schema partially compensates.

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 the schema already explains all parameters. The main description adds no additional meaning beyond what the schema provides, resulting in a baseline score.

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 the tool gets change history for a specific CVE or all changes within a date range, distinguishing it from sibling tools like get_cve or search_cves which focus on CVE data retrieval.

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 historical changes but lacks explicit guidance on when to use this tool versus alternatives, such as when a date range is needed or when to use search_cves instead.

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