cybersecurity-vuln-mcp

vuln_epss_top

Retrieve CVEs with EPSS exploitation probability above a threshold. Sort by highest score to prioritize vulnerabilities.

Instructions

Get CVEs with highest EPSS exploitation probability scores.

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

Input Schema

Name	Required	Description	Default
`threshold`	No	Minimum EPSS score (0-1)
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Apr 6, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the tool retrieves top-scoring CVEs but does not explain the role of threshold and limit parameters, or describe the output format. Important behavioral aspects like pagination or sorting order are omitted.

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?

The description is a single, efficient sentence. However, its brevity sacrifices necessary detail, making it feel incomplete rather than concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 parameters, no output schema), the description is insufficient. It does not explain the return value structure, how the threshold and limit interact, or typical usage. A more complete description would include the output format and the relationship between parameters.

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

Parameters2/5

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

The input schema already describes both 'threshold' and 'limit' parameters, but the context indicates only 50% schema description coverage. The description does not add any additional meaning or context for the parameters beyond what is in the schema, failing 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?

The description 'Get CVEs with highest EPSS exploitation probability scores' clearly indicates the tool returns top CVEs ranked by EPSS score. It is a specific verb-resource combination that distinguishes it from sibling tools like vuln_search or vuln_lookup_cve. However, it could be more explicit about the descending order and the inclusion of parameters.

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?

No guidance is provided on when to use this tool versus alternatives, such as vuln_search or vuln_by_vendor. There is no mention of prerequisites, limitations, or scenarios where this tool is not appropriate.

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

Deploy Server