Skip to main content
Glama
roadwy

cve-search_mcp

vul_last_cves

Retrieve JSON data of recent CVEs, including CAPEC, CWE, and CPE details, by specifying the number of entries to fetch.

Instructions

To get a JSON of the last <number> (5 by default) CVEs including CAPEC, CWE and CPE expansions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
numberNo

Implementation Reference

  • main.py:63-69 (handler)
    The handler function for the 'vul_last_cves' tool. It constructs the API URI for the last N CVEs and calls the get_requests helper to fetch the data from the CVE search API.
    @mcp.tool()
    def vul_last_cves(number: int = 5) -> List[Dict[str, Any]]:
        """
        To get a JSON of the last <number> (5 by default) CVEs including CAPEC, CWE and CPE expansions
        """
        uri = f"last/{number}"
        return get_requests(uri)
  • main.py:15-26 (helper)
    Helper function used by vul_last_cves (and other tools) to make HTTP GET requests to the CVE API, handling errors and returning JSON or error dict.
    def get_requests(uri: str) -> Dict[str, Any]:
        """To get a JSON with all the requests"""
        session = requests.Session()
        url = f"{BASE_URL}{uri}"
        try:
            response = session.get(url, timeout=15)
            response.raise_for_status()
            return response.json()
        except requests.exceptions.RequestException as e:
            logger.error(f"api request failed: {url} - {str(e)}")
            return {"error": str(e)}
  • main.py:63-63 (registration)
    The @mcp.tool() decorator registers the vul_last_cves function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool returns JSON with specific expansions (CAPEC, CWE, CPE), but lacks details on permissions, rate limits, error handling, or whether it's a read-only operation. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence that front-loads the key information: purpose, parameter role, and output format. There is no wasted text, and it directly communicates the essential details without redundancy or fluff.

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 complexity (retrieving CVEs with expansions), lack of annotations, no output schema, and low parameter schema coverage, the description is insufficient. It doesn't explain the structure of the returned JSON, error conditions, or how expansions are handled. For a tool with no structured support, more context is needed to be complete.

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?

The description adds some meaning beyond the input schema, which has 0% coverage. It explains that the 'number' parameter controls how many CVEs to retrieve and specifies a default of 5. However, it doesn't detail constraints (e.g., min/max values) or format expectations. With low schema coverage, this provides basic but incomplete compensation.

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 clearly states the tool's purpose: 'To get a JSON of the last <number> CVEs including CAPEC, CWE and CPE expansions.' It specifies the verb ('get'), resource ('CVEs'), and scope ('last <number>'), though it doesn't explicitly differentiate from sibling tools like 'vul_cve_search' or 'vul_vendor_product_cve'. This makes it clear but not fully sibling-distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions the default number (5) but doesn't indicate scenarios where this tool is preferred over siblings like 'vul_cve_search' or 'vul_vendor_product_cve'. There is no mention of prerequisites, exclusions, or comparative use cases.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/roadwy/cve-search_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server