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

cybersecurity-vuln-mcp

by martc03
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vuln_kev_due_soon

Find CISA Known Exploited Vulnerabilities (KEV) that require remediation within a specified number of days.

Instructions

Get CISA KEV vulnerabilities with upcoming remediation deadlines.

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_kev_due_soon"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoDeadline within next N days
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided. Description describes a read operation ('Get') but lacks details on authentication, rate limits, result ordering, pagination, or behavior when no results are found. Minimal behavioral disclosure.

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?

Single sentence, no unnecessary words. However, it may be too concise, sacrificing completeness. Structure is fine.

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 no output schema, no annotations, and partial schema coverage, the description is insufficient. Missing information on return format, sorting, or interpretation of 'upcoming remediation deadlines'. Incomplete for effective tool selection.

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?

Schema coverage is 50% (days parameter has description, limit does not). The tool description does not add any meaning beyond the schema; it does not explain how 'days' relates to 'due soon' or the role of 'limit'. No enrichment provided.

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?

Description clearly states the tool retrieves CISA KEV vulnerabilities with upcoming remediation deadlines. It uses specific verb 'Get' and resource 'CISA KEV vulnerabilities', distinguishing it from siblings like vuln_kev_latest which focuses on latest entries.

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?

The description implies usage for upcoming deadlines but provides no explicit guidance on when to use this tool versus alternatives like vuln_kev_latest or other sister tools. No when-not-to-use or contextual prerequisites are 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