Skip to main content
Glama

list_security_incidents

Read-only

Retrieve security incidents filtered by severity, state, or category to support triage and prioritization of security cases.

Instructions

List security incidents with filters (severity, state, category)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records to return (default 25)
queryNoAdditional encoded query string
stateNoFilter by state: open (any active), draft, analysis, contain, eradicate, recover, review, closed, cancelled, or the number
categoryNoFilter by incident category
severityNoFilter by severity (1=High, 2=Medium, 3=Low)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.1.0
    • changedInput schema / properties / state / description
      Previous value: -"Filter by state (open, analysis, contain, eradicate, recover, review, closed)"New value: +"Filter by state: open (any active), draft, analysis, contain, eradicate, recover, review, closed, cancelled, or the number"
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered, but the description adds nothing beyond that: no mention of pagination behavior tied to the limit parameter, no default sort order, and no statement about whether results are scoped to the caller's workspace. For a listing tool whose volume can be large, this leaves real behavioral questions unanswered.

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?

A single short, front-loaded phrase with parenthetical filter enumeration and zero redundant wording. It is efficient, though the terseness is close to under-specification rather than exemplary concision.

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?

For a simple read-only list tool with full schema documentation and no output schema, the description is minimally sufficient to call it. It is missing return-shape hints, ordering, and pagination cues that would matter for an unpaginated-looking list endpoint.

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 description coverage is 100%, including the severity code mapping and the full state enum, so the schema already carries parameter meaning. The description merely repeats three of the five filter names and adds no syntax, combination rules, or default behavior beyond what the schema states.

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?

States a specific verb ('List') and resource ('security incidents') and names the filter dimensions, so an agent knows immediately what the tool returns. It does not distinguish itself from siblings such as get_security_incident (singular fetch) or ml_forecast_incidents, leaving that differentiation to the agent.

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?

There is no when-to-use or when-not-to-use guidance: nothing says to prefer this over get_security_incident for a single record or over the ml_* incident tools for predictions. The only hint is the word 'List', which is implied usage at best, and no prerequisites or exclusions are stated.

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