Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

cyber_cve_kev_epss_vulnerability_scanner

Read-onlyIdempotent

CVE Vulnerability CISA KEV EPSS Exploit API: Real-time CISA Known Exploited Vulnerabilities (KEV) and FIRST EPSS exploitation probability scoring feed.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum vulnerability records to return (1-50, default: 10).
queryNoTarget CVE ID, vendor, or software product keyword (e.g., "CVE-2024", "apache", "microsoft").apache
minScoreNoMinimum EPSS exploit probability score (0.0 to 1.0).
severityNoSeverity level filter ("ALL", "CRITICAL", "HIGH", "MEDIUM").CRITICAL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
      +  "default": 10,
      +  "description": "Maximum vulnerability records to return (1-50, default: 10).",
      +  "type": "integer"
      +}
    • removedInput schema / properties / maxResults
      Removed value: -{
      -  "default": 10,
      -  "description": "Maximum number of structured items to extract.",
      -  "type": "integer"
      -}
    • addedInput schema / properties / minScore
      Added value: +{
      +  "default": 0.2,
      +  "description": "Minimum EPSS exploit probability score (0.0 to 1.0).",
      +  "type": "number"
      +}
    • addedInput schema / properties / query
      Added value: +{
      +  "default": "apache",
      +  "description": "Target CVE ID, vendor, or software product keyword (e.g., \"CVE-2024\", \"apache\", \"microsoft\").",
      +  "type": "string"
      +}
    • addedInput schema / properties / severity
      Added value: +{
      +  "default": "CRITICAL",
      +  "description": "Severity level filter (\"ALL\", \"CRITICAL\", \"HIGH\", \"MEDIUM\").",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety and idempotency profile is covered. The description adds only one behavioral trait beyond that — 'Real-time' indicating data freshness — and says nothing about upstream rate limits, coverage gaps (KEV only lists known-exploited CVEs, so absence is not proof of safety), or the shape of results.

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?

It is a single compact sentence with the two data sources front-loaded and no filler. It is jargon-dense and repeats the tool name's own terms ('CVE Vulnerability', 'Exploit API'), which costs a little clarity but no padding.

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 read-only, zero-required-parameter lookup with fully documented schema and complete annotations, the definition is minimally viable. It still omits how the tool behaves operationally — keyword matching semantics for 'query', what a returned record contains (KEV flag plus EPSS score), and how it differs from adjacent CVE scanners — leaving real gaps for an agent picking among many similar vulnerability tools.

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 (limit, query, minScore, severity) is already documented with ranges and defaults, making 3 the baseline. The description contributes only an implicit mapping between 'EPSS exploitation probability scoring' and the minScore parameter; it adds no syntax, defaults, or edge-case meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the data sources precisely (CISA KEV and FIRST EPSS probability scoring), which identifies the resource well, but it never states the action: nothing says this searches/filters CVE records by CVE ID, vendor, or product keyword. It also does not distinguish itself from sibling CVE scanners such as shodan_internetdb_zero_key_ip_port_cve_scanner or vpn_gateway_firewall_cve_exposure_scanner, leaving the agent to infer the boundary from the name alone.

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 guidance, no when-not-to-use guidance, and no mention of alternatives, despite several sibling CVE/vulnerability tools existing. The phrase 'Real-time ... feed' hints at live data but gives no conditions that would select this tool over its siblings.

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.

Resources