Skip to main content
Glama

cve_intel

Retrieve CVE details, CVSS, CWE, EPSS score, and CISA KEV status to assess vulnerability severity and exploitation risk.

Instructions

CVE intelligence: description, CVSS, CWE, EPSS score and CISA KEV status.

Combines CIRCL CVE, FIRST EPSS and the CISA Known Exploited Vulnerabilities catalogue, with NVD as a fallback. Keyless.

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

Input Schema

NameRequiredDescriptionDefault
cve_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/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 burden, and it does disclose useful behavior: the three upstream sources combined (CIRCL CVE, FIRST EPSS, CISA KEV), NVD as fallback, and that it is keyless (no auth setup needed). It omits rate limits, timeout behavior, and what happens for an unknown or malformed CVE ID.

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?

Three short lines, front-loaded with the resource and the returned fields, then source/fallback detail. No filler sentences; only the trailing blank-line formatting is wasted.

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?

For a simple single-parameter read tool with no output schema, listing the returned fields is the right move, and the fallback chain adds confidence in result availability. Missing are input format expectations and the failure mode when a CVE is not found, which an agent needs to interpret an empty response.

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?

Only one parameter (cve_id) with 0% schema description coverage, and the description adds no format guidance such as CVE-YYYY-NNNN. The parameter is largely self-explanatory from its name, but the description does nothing to compensate for the coverage gap.

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 resource (CVE) and enumerates exactly what it returns: description, CVSS, CWE, EPSS score and CISA KEV status. That is clearly distinct from the ip_intel/email_intel-style siblings, though the description never names an alternative to route against.

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?

Usage is only implied: an agent infers 'use this to look up a CVE by ID'. There is no explicit when-to-use, when-not-to-use, or alternative named for related lookups (e.g. IP or vendor intel).

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