Skip to main content
Glama
Sign In
cve-cache-mcp

cve-cache-mcp

by weiseer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_recent_critical

Get recent high-severity CVEs (CVSS ≥ 7) from the past week, with adjustable severity and time range to find critical vulnerabilities.

Instructions

Recent CVEs with CVSS >= threshold. Default: 7-day high-severity 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": "list_recent_critical"
  }
}

Input Schema

NameRequiredDescriptionDefault
min_cvssNo
since_daysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided. Description hints at default behavior (7 days, high severity) but lacks details on pagination, output format, or other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise, two sentences. Front-loaded with key purpose and default behavior. No redundant text.

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

Completeness1/5

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

No output schema, no parameter descriptions, no annotations. Description is too minimal for an agent to reliably understand the tool's full behavior and output.

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?

0% schema description coverage. Description implies min_cvss and since_days roles via 'CVSS >= threshold' and 'default: 7-day', but doesn't explicitly explain either parameter.

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

Purpose5/5

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

Clearly states it lists recent CVEs with CVSS >= threshold and defaults to 7-day high-severity feed. Distinguishes from siblings (lookup_cve, find_for_package, severity_summary) by focusing on recency and severity filter.

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 explicit guidance on when to use this tool vs siblings. Defaults are given but no conditions or exclusions mentioned.

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

Deploy Server

Other Tools