Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

scan_cve_kev_epss_vulnerabilities

Read-onlyIdempotent

Correlate CVEs with CISA KEV, EPSS exploit probabilities, and CVSS severity to prioritize vulnerabilities for remediation and filter results by vendor or minimum EPSS score.

Instructions

Correlate Common Vulnerabilities and Exposures (CVEs) against the CISA Known Exploited Vulnerabilities (KEV) catalog, FIRST.org 30-day Exploit Prediction Scoring System (EPSS) probabilities, and NVD CVSS v3 severity metrics.

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

Input Schema

NameRequiredDescriptionDefault
cveIdsNoOptional list of specific CVE identifiers (e.g., ["CVE-2024-3094", "CVE-2023-44487"]). Leave empty to scan latest CISA KEV additions.
maxResultsNoMaximum number of prioritized vulnerability records to return.
minEpssScoreNoMinimum 30-day FIRST.org EPSS exploitation probability between 0.0 and 1.0.
vendorFilterNoOptional vendor or product filter (e.g., "Microsoft", "Cisco", "Fortinet", "Linux").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds the meaningful behavioral fact that results are a correlation across three external feeds, but it says nothing about how records are ranked or ordered, freshness of the feeds, or failure behavior when a source is unavailable.

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?

One front-loaded sentence with no filler or hedging. The acronym expansions are slightly token-heavy but serve disambiguation across three similarly named standards. It could have been split or shortened, but nothing is redundant.

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 four optional parameters, no output schema, and read-only annotations, the description covers the data sources but not the return shape — an agent cannot tell whether it gets a ranked priority list, per-CVE source flags, or raw CVSS vectors. For a scan tool with no output schema, that is a real gap, though not a blocking one.

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 every parameter including the EPSS threshold and vendor filter is already documented in the schema. The description adds no syntax, default, or interaction detail beyond that. Baseline 3 applies when the schema carries the parameter burden.

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?

The definition uses a specific verb ("Correlate") with a specific resource (CVEs) and enumerates the three data sources joined: CISA KEV, FIRST.org EPSS, and NVD CVSS v3. This is far more informative than a name restatement. It does not explicitly differentiate itself from siblings, but the enumerated sources make its domain unmistakable.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no alternatives named. The only usage signal — that an empty cveIds list scans latest KEV additions — lives in the schema, not the description. An agent must infer the vulnerability-prioritization use case.

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