Skip to main content
Glama

Enrich a CVE

enrich_cve
Read-only

Full intelligence for a single CVE: CVSS, KEV status, EPSS, CISA SSVC (exploitation/automatable/technical_impact), P1-P4 priority with rationale, affected products/versions, Debian/Ubuntu/Alpine fixed builds per release (distro_fixes), and (live) public-exploit signal.

For a LIST (a scan's findings, a vulnerability review): pass cve_ids (up to 50) instead and get one compact card per CVE with the exploitation evidence only: KEV (+ date added, ransomware use), SSVC, EPSS, Metasploit modules, the danger signal when KEV is silent, CVSS vector. Whether each applies to a given host is a separate verify_cve_claim with that host's product/build.

Args: cve_id: e.g. "CVE-2025-12345". include_poc: also query GitHub for public PoC/exploit repos (live; single CVE only). cve_ids: a list of CVE ids for compact list mode (max 50).

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

Input Schema

NameRequiredDescriptionDefault
cve_idNo
cve_idsNo
include_pocNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / cve_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / cve_id / default
      Added value: +null
    • removedInput schema / properties / cve_id / type
      Removed value: -"string"
    • addedInput schema / properties / cve_ids
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Cve Ids"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "cve_id"
      -]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real operational context on top: include_poc triggers a live GitHub query and is single-CVE only, and list mode is capped at 50 ids with a deliberately reduced evidence set. It does not mention rate limits, latency, or failure behavior for unknown/unmatched CVE ids, which keeps it from a 5.

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?

Front-loaded with the high-value single-CVE summary, then the list-mode paragraph, then per-argument notes — a sensible order with little waste. The enumerated field list is dense but each item is informative; a few phrases like 'with rationale' and '(live)' are slightly repetitive with the Args section.

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?

No output schema exists, so the description must describe returns and it does thoroughly for both modes, down to the fields in a compact card. Comparable completeness holds for inputs and for the hand-off to verify_cve_claim; the only real gap is undefined behavior when neither cve_id nor cve_ids is supplied, which matters because no parameter is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden and largely does: it defines the cve_id format with an example, explains that include_poc adds live GitHub PoC lookup and applies only in single mode, and states the 50-item ceiling for cve_ids along with the compact-card output shape. It implies but never states outright that the two id parameters are alternatives, leaving one ambiguity.

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?

Names a specific verb and resource ('Full intelligence for a single CVE') and then enumerates the exact fields returned: CVSS, KEV, EPSS, SSVC, P1-P4 priority, distro_fixes, exploit signal. It also explicitly distinguishes the single-CVE path from the list path and points host-applicability questions to the sibling verify_cve_claim, so an agent can pick correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit routing: one CVE → cve_id; a scan's findings or a vulnerability review list → cve_ids (up to 50); whether a finding applies to a given host → verify_cve_claim with that host's product/build. Both the when and the when-not (with a named alternative) are stated.

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.