Skip to main content
Glama

history_listIncidents

Query historic incidents, including resolved ones, and filter by process instance, type, or resolution state to support post-incident analysis.

Instructions

Query historic incidents including resolved ones. Filter by process instance, type, or resolution state. Use for post-incident analysis.

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

Input Schema

NameRequiredDescriptionDefault
openNo
sortByNo
deletedNo
resolvedNo
sortOrderNo
activityIdNo
incidentIdNo
maxResultsNo
tenantIdInNo
executionIdNo
firstResultNo
endTimeAfterNo
incidentTypeNo
configurationNo
endTimeBeforeNo
causeIncidentIdNo
createTimeAfterNo
incidentMessageNo
withoutTenantIdNo
createTimeBeforeNo
failedActivityIdNo
jobDefinitionIdInNo
processInstanceIdNo
incidentMessageLikeNo
processDefinitionIdNo
rootCauseIncidentIdNo
historyConfigurationNo
processDefinitionKeyNo
processDefinitionKeyInNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed29 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 / createTimeAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createTimeBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deleted
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / endTimeAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / endTimeBefore
      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 / historyConfiguration
      Added value: +{
      +  "type": "string"
      +}
    • 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 / incidentType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / jobDefinitionIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / open
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionKeyIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / resolved
      Added value: +{
      +  "type": "boolean"
      +}
    • 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"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral context. It usefully discloses that resolved incidents are included, which matters for historical analysis, but says nothing about read-only behavior, pagination, sorting, tenant scoping, rate limits, or authentication.

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 short sentences with the primary purpose and a usage cue front-loaded. It is efficiently written, though it is so terse relative to the large parameter set that conciseness edges toward under-specification.

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 29-parameter query tool with no annotations and no output schema, the description is far from complete. It does not explain the rich filtering surface, pagination behavior, sorting, or what result shape an agent should expect.

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 29 parameters, so the description must explain parameter meaning. It mentions only process instance, incident type, and resolution state, leaving most parameters such as sorting, pagination, time ranges, tenant filters, and incident IDs 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?

The description states a specific verb and resource: query historic incidents, including resolved ones. This clearly distinguishes the tool from a current-incident listing by scope, though it does not explicitly name or contrast the sibling incident_list tool.

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?

It gives one usage signal, 'Use for post-incident analysis,' which implies when this tool is appropriate. However, it does not explain when to prefer incident_list, when not to use this tool, or any prerequisites for querying history.

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