Skip to main content
Glama

cisa-cybersecurity-mcp-server

cisa_get_alerts

cisa_get_alerts
Read-onlyIdempotent

List recent CISA publications from the combined advisories, alerts, or ICS advisories feed. Cursors continue within the available 30-item rolling window. Upstream provides no pagination, history, or date-range query. See window.oldest and window.newest for the dates the window covers. For ICS advisory history beyond the window, use cisa_search_ics_advisories.

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

Input Schema

NameRequiredDescriptionDefault
feedNoPublication feed to read. Choose advisories for combined advisories, alerts for CISA alerts, or ics for ICS advisories. See window.oldest and window.newest for coverage dates.advisories
limitNoMaximum items to return; values above 30 use 30 when input clamping is enabled. The upstream window contains at most 30 items.
sinceNoKeep only items published on or after this date, YYYY-MM-DD. Filters within the fetched window; it cannot reach back beyond it.
cursorNoOpaque continuation cursor from this feed. Resumes after the last returned GUID within the available window; omit to restart.
detailNoUse summary for capped descriptions or full for complete feed descriptions where no advisory ID is available. A capped item with an advisory ID can be read with cisa_get_advisory.summary

Output Schema

NameRequiredDescriptionDefault
capNoThe limit that was applied.
feedNoThe feed that was read.
errorNoPresent when the call failed. Absent on success.
itemsNoItems from the fetched window, newest first as published; stale identifies cached fallback.
shownNoItems returned.
staleNoTrue when refresh failed and this response uses the last cached window.
cursorNoContinuation cursor for this feed; absent on the last page or when the anchor is unavailable.
noticeNoSafe retry guidance on refresh failure, or guidance when the since filter excluded every item.
windowNoWhat the fetched window covers.
feedUrlNoThe absolute feed URL this window came from.
hasMoreNoWhether more matching items remain after this page within the available window.
feedTitleNoThe channel title the feed declares.
fetchedAtNoUTC timestamp when this window was successfully fetched.
truncatedNoTrue when the limit capped the returned items.
windowCaveatNoLimits of continuation within the upstream rolling window.
effectiveQueryNoThe since filter as applied, and how many window items it excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / detail
      Added value: +{
      +  "default": "summary",
      +  "description": "Use summary for capped descriptions or full for complete feed descriptions where no advisory ID is available. A capped item with an advisory ID can be read with cisa_get_advisory.",
      +  "enum": [
      +    "summary",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / feed / description
      Previous value: -"Which feed to read: advisories (all.xml, ~8 days of coverage), alerts (alerts.xml, ~8 weeks), or ics (ics-advisories.xml, ~2.5 weeks)."New value: +"Publication feed to read. Choose advisories for combined advisories, alerts for CISA alerts, or ics for ICS advisories. See window.oldest and window.newest for coverage dates."
    • addedOutput schema / properties / items / items / properties / guidance
      Added value: +{
      +  "description": "Advisory lookup to use when the description remains capped in full detail.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / items / items / properties / summary / description
      Previous value: -"Item description with HTML stripped and entities decoded, capped at 1,200 characters."New value: +"Item description with HTML stripped and entities decoded. Capped at 1,200 characters unless detail is full and the item has no advisoryId."
  2. Changed9 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "Opaque continuation cursor from this feed. Resumes after the last returned GUID within the available window; omit to restart.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum items to return. The 30 ceiling is the upstream window, not a server choice."New value: +"Maximum items to return; values above 30 use 30 when input clamping is enabled. The upstream window contains at most 30 items."
    • changedInput schema / properties / limit / maximum
      Previous value: -30New value: +1000
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "stale",
      -      "fetchedAt",
      -      "feed",
      -      "feedUrl",
      -      "feedTitle",
      -      "items",
      -      "window",
      -      "windowCaveat"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "hasMore",
      +      "stale",
      +      "fetchedAt",
      +      "feed",
      +      "feedUrl",
      +      "feedTitle",
      +      "items",
      +      "window",
      +      "windowCaveat"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / cursor
      Added value: +{
      +  "description": "Continuation cursor for this feed; absent on the last page or when the anchor is unavailable.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `feed_unavailable`: The feed fetch failed or returned a body that carried no RSS channel. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `read_limit_exceeded`: limit exceeds the per-call cap and input clamping is disabled. `invalid_cursor`: The cursor is malformed or belongs to a different feed. `feed_unavailable`: The feed fetch failed or returned a body that carried no RSS channel. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "feed_unavailable"
      -]New value: +[
      +  "read_limit_exceeded",
      +  "invalid_cursor",
      +  "feed_unavailable"
      +]
    • addedOutput schema / properties / hasMore
      Added value: +{
      +  "description": "Whether more matching items remain after this page within the available window.",
      +  "type": "boolean"
      +}
    • changedOutput schema / properties / windowCaveat / description
      Previous value: -"That the feed has no history, no pagination, and no date query."New value: +"Limits of continuation within the upstream rolling window."
  3. Changed7 schema fields changed
    • addedInput schema / properties / since / format
      Added value: +"date"
    • changedInput schema / properties / since / pattern
      Previous value: -"^\\d{4}-\\d{2}-\\d{2}$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "feed",
      -      "feedUrl",
      -      "feedTitle",
      -      "items",
      -      "window",
      -      "windowCaveat"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "stale",
      +      "fetchedAt",
      +      "feed",
      +      "feedUrl",
      +      "feedTitle",
      +      "items",
      +      "window",
      +      "windowCaveat"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / fetchedAt
      Added value: +{
      +  "description": "UTC timestamp when this window was successfully fetched.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / items / description
      Previous value: -"Items from the current window, newest first as published."New value: +"Items from the fetched window, newest first as published; stale identifies cached fallback."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when the since filter excluded every item."New value: +"Safe retry guidance on refresh failure, or guidance when the since filter excluded every item."
    • addedOutput schema / properties / stale
      Added value: +{
      +  "description": "True when refresh failed and this response uses the last cached window.",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • changedOutput schema / properties / items / items / properties / advisoryId / pattern
      Previous value: -"^ICS(A|MA)-\\d{2}-\\d{3}-\\d{2}(?:[a-z]|-\\d+)?$"New value: +"^ICS(A|MA)-\\d{2}-\\d{3}-\\d{2}(?:[A-Z]|-\\d+)?$"
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly and idempotent; the description goes well beyond them by disclosing the 30-item rolling window, cursor continuation semantics within that window, and the absence of upstream pagination or history. It also points to window.oldest/newest so the agent knows how to detect the coverage boundary.

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?

Five short sentences, front-loaded with purpose before constraints and the alternative. The window.oldest/newest coverage point is stated in both the description and the feed parameter, a minor redundancy but nothing extraneous overall.

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

Completeness5/5

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

Output schema exists, so return-structure explanation is unnecessary, and the description still names the window fields that bound results. For a five-parameter, zero-required list tool with a hard 30-item cap, every operational caveat an agent needs (cap, no history, cursor scope, filter limits) is covered.

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?

Schema coverage is 100%, so the enum values and the since/cursor/limit constraints are already documented in the schema. The description reinforces the same window constraints (cursor continues within the window) but adds no syntax or interpretation details the schema lacks, so baseline 3 applies.

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 ('List recent CISA publications') plus the three selectable feeds, and explicitly names the sibling it does not cover for deep history. An agent can distinguish it from cisa_search_ics_advisories without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit alternative and the condition that selects it ('For ICS advisory history beyond the window, use cisa_search_ics_advisories') and states the negative constraint that upstream offers no pagination, history, or date-range query. Leaves little to inference about when this tool is the wrong choice.

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.