Skip to main content
Glama

circl_cve_recent

Read-onlyIdempotent

Retrieve recently published CVE vulnerabilities from CIRCL to monitor new security exposures and prioritize remediation.

Instructions

Get the most recently published CVE vulnerabilities from CIRCL.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing operational beyond the word 'recent' — no result count, no time window (hours? days?), no pagination, and no note that the upstream CIRCL feed may lag. For a zero-parameter feed tool the freshness contract is the key behavior and it is missing.

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?

A single front-loaded sentence with no waste or filler. It is appropriately sized, though it is so terse that useful context was cut rather than trimmed.

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?

With no parameters and no output schema, the description must carry the burden of explaining what comes back. It says the results are 'most recently published' but not how many entries, what fields each CVE record contains, or how recency is defined — gaps that matter for an agent deciding between this and a targeted CVE lookup.

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?

The tool takes zero parameters, which is the baseline-4 case; there is nothing for the description to disambiguate. The description correctly implies the tool needs no input arguments to fetch the latest feed.

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 ('Get the most recently published CVE vulnerabilities') and names the source (CIRCL), so the operation is unambiguous. It does not, however, distinguish itself from nearby siblings such as get_recent_cves, search_cve, or circl_cve_lookup, which an agent would need help disambiguating.

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 statement of when to use this versus search_cve, get_cve_detail, or get_recent_cves, and no exclusions or prerequisites. The agent is left to infer that this is a 'browse the latest feed' tool rather than a targeted lookup.

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