Skip to main content
Glama

Patchfirst

Newest CVEs

list_feed
Read-onlyIdempotent

Newest CVEs by published date, with KEV/EPSS/CVSS (source data) and priority. Complete for the last 30 days (every CVE published in that window is core tier); older dates list core-tier CVEs only. Filter by a since-date and minimum CVSS severity.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax results, default 20, max 100.
sinceNoOnly CVEs published on/after this date (YYYY-MM-DD).
min_severityNoMinimum CVSS base severity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the bar is lower. The description still adds non-obvious semantics: results are complete for the last 30 days but degrade to core-tier-only for older dates, which materially affects how an agent should interpret and trust the output. It omits pagination behavior beyond the limit default, which the schema covers.

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 compact sentences, front-loaded with what the tool returns before the coverage caveat and the filters. The parenthetical '(source data)' and the undefined 'core tier' term are slightly opaque, but nothing is redundant.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns, and it does name the enrichment fields (KEV/EPSS/CVSS) plus a computed priority. Combined with fully documented parameters and clear safety annotations, an agent has enough to call this correctly; only the ranking of 'priority' and pagination remain unexplained.

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 the baseline is 3. The description does add meaning by framing 'since' as the switch that changes result completeness rather than a simple filter, but it adds nothing about limit or the severity enum beyond the schema text.

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 and ordering: newest CVEs by published date, enriched with KEV/EPSS/CVSS and priority. This is clearly distinct from the sibling names suggesting technique-scoped (cves_for_technique) or exploited-only (list_exploited) queries, but the description never names those alternatives explicitly, so differentiation is implicit.

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?

It gives concrete filtering guidance ('Filter by a since-date and minimum CVSS severity') and defines the coverage window, which tells the agent how to scope a request. It does not say when to prefer this over list_exploited or cves_for_technique, so selection among siblings is left to inference.

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