Skip to main content
Glama

get_latest_alerts

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 observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description must carry behavioral disclosure. It establishes that the source is a free public catalog and that results are filtered views, which implies a read-only operation, but it never states that the tool is non-destructive, whether there are rate limits or auth needs, or how fresh "recent" actually is — a material gap for a tool whose whole value is timeliness. Return values are covered by the output schema, so that omission is acceptable.

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 purpose is front-loaded in one sentence, then the three parameters are covered in a compact block with no marketing filler or repetition. Every line adds information the schema does not already contain.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter read tool with an output schema and no annotations, the definition covers purpose, source, and all parameters adequately. The only real gap is the undefined time window behind "latest," which an agent would need to describe results confidently, but overall it is sufficient to call the tool correctly.

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 supply all parameter meaning, and it does: it gives the valid range (1–15) and default (5) for limit, explains that consumer_only narrows to everyday devices and browsers with vendor examples, and clarifies that keyword filters by product or vendor with sample values. It does not state how keyword interacts with consumer_only or whether matching is case-insensitive, keeping it below a 5.

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 names a specific verb and resource ("Get recent actively exploited security alerts") and identifies the data source ("free CISA KEV catalog"), which cleanly separates it from siblings like check_password_hygiene or analyze_scam_message. It stops short of explicitly contrasting itself with any named alternative, but the subject matter alone makes the tool's role unambiguous.

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 implied by the domain — fetching recent exploited-vulnerability alerts — and "in plain English" hints at a non-technical audience, but there is no explicit when-to-use statement, no exclusion of cases (e.g. personal breach alerts), and no pointer to siblings. An agent can infer the fit but must do the work itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.