Skip to main content
Glama

first-epss-mcp-server

Epss Query Threshold

epss_query_threshold
Read-onlyIdempotent

Discover CVEs using inclusive EPSS or percentile bounds, CVE year or dataset-addition recency; filters intersect and at least one is required. Examine one candidate page in the upstream FIRST order, which is not ranked by EPSS, so the first page does not hold the highest scores. Each serialized response surface fits 65536 UTF-8 bytes; budgetLimited and withheldCount disclose whole matches withheld, with nextOffset at the first withheld match. Year filtering can return an empty page with nextOffset; candidateTotal is a broad-query total, not an exact-year total. Continue with the same filters, limit, returned score date and nextOffset.

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

Input Schema

NameRequiredDescriptionDefault
dateNoUTC date YYYY-MM-DD from 2021-04-14 through today; omitted or blank selects latest available data.
yearNoExact CVE year from 1999 through the current UTC year; candidate pages may contain no matches.
limitNoRequested candidates per page; positive safe integers above 10000 are clamped to 10000 before exact-year filtering.
offsetNoCandidate-space offset; use returned nextOffset for continuation.
maxEpssNoInclusive maximum EPSS probability.
minEpssNoInclusive minimum EPSS probability.
maxPercentileNoInclusive maximum population percentile rank.
minPercentileNoInclusive minimum population percentile rank.
addedWithinDaysNoDataset-addition recency relative to upstream present, independent of historical date.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoMissing-data, deferred-work or model-metadata caveats.
scoresNoRetained records from this candidate page.
filtersNoApplied filters; combine with provenance scoreDates to pin continuation.
paginationNoCandidate pagination accounting.
provenanceNoSnapshot source and model metadata, including dates from filtered-out candidates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: upstream FIRST ordering is not EPSS-ranked, pages are capped at 65536 UTF-8 bytes, budgetLimited/withheldCount report withheld whole matches, and nextOffset points at the first withheld match. It also warns that year filtering can yield empty pages and that candidateTotal is a broad-query total, none of which the annotations or schema disclose.

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?

Dense but front-loaded: pagination/ordering caveats come before the continuation rule, and each clause conveys operational detail. Some sentences are compressed to the point of being hard to parse ('Each serialized response surface fits 65536 UTF-8 bytes'), but there is no filler.

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

Completeness5/5

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

For a nine-parameter discovery tool with high schema coverage and an output schema, the description supplies the missing pieces: cross-parameter AND semantics, the implicit at-least-one-filter requirement, page-size budget behavior, ordering caveats, and exact resume semantics. An agent can page correctly and interpret withheld counts without guessing.

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 100%, so the baseline is 3; the description adds meaning by explaining that filters intersect (AND semantics), that at least one must be supplied despite zero required params, and that offset is in candidate space with nextOffset at the first withheld match. It does not clarify the distinction between date and addedWithinDays beyond what the schema already states.

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 verb and resource: 'Discover CVEs using inclusive EPSS or percentile bounds, CVE year or dataset-addition recency.' The scope, including which filters are available, is clear enough to separate it from epss_get_scores, but no sibling is named, so an agent must infer that this is the discovery/search tool and the other returns scores for known CVEs.

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

Usage Guidelines4/5

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

Gives real usage constraints: filters intersect, at least one is required, and continuation must reuse the same filters, limit, score date and nextOffset. It does not explicitly state when to prefer this over epss_prioritize_cves or epss_get_scores, but the constraints and pagination instructions make correct invocation possible.

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.