Skip to main content
Glama

incident_list

Lists active incidents in the Operaton engine so you can filter failed jobs, scripts, or custom conditions by type, message, process definition, or activity ID.

Instructions

List active incidents in the engine. Filter by type, message, process definition, or activity. Incidents indicate failed jobs, failed scripts, or custom conditions.

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

Input Schema

NameRequiredDescriptionDefault
sortByNo
sortOrderNo
activityIdNo
incidentIdNo
maxResultsNo
tenantIdInNo
executionIdNo
firstResultNo
incidentTypeNo
configurationNo
causeIncidentIdNo
incidentMessageNo
failedActivityIdNo
jobDefinitionIdInNo
processInstanceIdNo
incidentMessageLikeNo
processDefinitionIdNo
rootCauseIncidentIdNo
incidentTimestampAfterNo
processDefinitionKeyInNo
incidentTimestampBeforeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv1.3.0
    • addedInput schema / properties / activityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / causeIncidentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / configuration
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / failedActivityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / incidentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / incidentMessage
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / incidentMessageLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / incidentTimestampAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / incidentTimestampBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / incidentType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobDefinitionIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionKeyIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / rootCauseIncidentId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations and no output schema, the description carries the full behavioral burden. It says the tool lists active incidents and explains what incidents represent, but it does not disclose read-only behavior, pagination, sorting, limits, permissions, or response shape.

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 description is three tight sentences and front-loads the core purpose before listing filters and incident meaning. It is appropriately sized, though it could pack slightly more useful parameter guidance into the same space.

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?

For a 21-parameter listing tool with no annotations, no output schema, and zero schema descriptions, the description is not complete enough. It omits most filter, sorting, paging, and identifier semantics that an agent needs in order to invoke the tool correctly.

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 description coverage is 0% across 21 parameters, so the description must compensate. It mentions filters by type, message, process definition, and activity, covering only a few parameters while leaving sorting, paging, tenant, execution, job definition, timestamp, and various incident identifier parameters undocumented.

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 and resource (list incidents) and scopes it to active incidents in the engine. It does not explicitly name sibling alternatives such as incident_getById or history_listIncidents, but the active-incident framing helps distinguish it from historical listing.

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?

The description explains what can be filtered but does not say when to use this tool versus incident_count, incident_getById, incident_resolve, or history_listIncidents. Usage is only implied by the word 'active' and the filter list.

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