Skip to main content
Glama
CyberSafe MCP

CyberSafe MCP

by kshitij9896

get_latest_alerts

Retrieve recent actively exploited security alerts from the CISA KEV catalog in plain English, with optional filters for consumer devices and product or vendor keywords.

Instructions

Get recent actively exploited security alerts from the free CISA KEV catalog in plain English.

Args: limit: Number of alerts to return (1 to 15, default 5). consumer_only: If True, focuses on everyday devices & browsers (Apple, Google, Microsoft, etc.). keyword: Optional product or vendor filter (e.g. 'Chrome', 'iPhone', 'Windows').

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

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordNo
consumer_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does establish that this is a free public-catalog read with a bounded result count (1–15, default 5) and a device-oriented filter, which usefully signals scope and volume. It omits freshness/staleness of the KEV data, whether the catalog is static or live, behavior on empty results, and result ordering beyond the word 'recent'.

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 opening sentence is front-loaded and earns its place with source, recency, and plain-English output. The docstring-style 'Args:' block is efficient and scannable, though it mixes parameter documentation into the description rather than prose guidance about selection.

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?

An output schema exists, so return-value explanation is not needed, and all three parameters are covered. What remains missing is material for a data-feed tool: freshness of the KEV list, whether results can be empty, and how consumer_only interacts with keyword filtering when both are supplied.

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?

Schema description coverage is 0%, so the description must compensate, and it largely does: it states the valid range for limit (1–15) beyond the schema's bare default, explains what consumer_only actually selects (everyday devices and browsers, with vendor examples), and gives concrete keyword examples like 'Chrome' and 'iPhone'. It still leaves keyword matching semantics (case sensitivity, partial vs exact, vendor vs product) unspecified.

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?

States a specific verb and resource ('Get recent actively exploited security alerts') plus the exact data source (free CISA KEV catalog) and output style (plain English). This is clearly distinct from every sibling, which deal with tips, scam messages, breaches, password hygiene, and URL safety rather than alert feeds.

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?

Usage is only implied: an agent can infer this is for looking up recent exploited vulnerabilities, and the consumer_only param hints at a consumer-vs-enterprise framing. There is no explicit when-to-use, when-not-to-use, or named alternative when a different tool would be better (e.g., for a specific URL or email).

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