Skip to main content
Glama
Sign In
cybersecurity-vuln-mcp

cybersecurity-vuln-mcp

by martc03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vuln_trending

Retrieves trending critical or high severity CVEs published within a configurable number of days for vulnerability tracking.

Instructions

Get recently published critical/high severity CVEs from the NVD.

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

Input Schema

NameRequiredDescriptionDefault
daysNoPublished within last N days
severityNoCRITICAL
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description must fully disclose behavior but only states the basic function. It omits details on rate limits, data freshness, response structure, or whether the operation is read-only.

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?

The description is a single, concise sentence that conveys the main purpose without extraneous details. However, it could be expanded slightly for clarity without losing conciseness.

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 has 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, pagination, or edge cases, leaving significant gaps for an agent.

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?

The description adds no value beyond the input schema. Schema coverage is low (33%), but the description doesn't explain parameter meanings or relationships, such as how 'days' and 'severity' interact.

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 verb 'Get' and the resource 'recently published critical/high severity CVEs from the NVD', effectively conveying the tool's purpose and distinguishing it from siblings like vuln_search. However, it inaccurately restricts severity to critical/high when the parameter allows all levels.

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 guidance on when to use this tool versus alternatives (e.g., vuln_by_vendor, vuln_search). The description does not specify contexts where this tool is preferred or when to avoid it.

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