Skip to main content
Glama

incident_count

Count active incidents matching filter criteria to assess operational health before investigating individual issues. Use filters such as process instance, type, or timestamp to scope the count.

Instructions

Count active incidents matching filter criteria. Use to gauge operational health before investigating individual incidents.

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_count"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 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 / 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 / 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 / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
  2. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses very little. It never defines what makes an incident 'active', says nothing about the return shape (scalar count), and gives no indication of permissions, data freshness, or whether unfiltered calls scan the entire tenant.

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?

Two short sentences, purpose first, usage second, with no filler or redundancy. Well front-loaded and easy to scan.

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?

Adequate for a read-only count, but with 17 undocumented parameters and no output schema, the description should have clarified the count return value and at least the most ambiguous filter families. An agent can guess a filter-based count but must still open the schema blind.

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?

The description only says filters exist; it adds zero meaning across 17 parameters at 0% schema description coverage. Ambiguous fields such as causeIncidentId vs rootCauseIncidentId, incidentMessage vs incidentMessageLike, and the *_In array-string semantics are left entirely unexplained.

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 ('count active incidents') plus scope ('matching filter criteria'), which clearly distinguishes it from incident_list and incident_getById. No further differentiation is offered, but the count-versus-list distinction is evident from the verb.

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?

'Use to gauge operational health before investigating individual incidents' gives a soft sequencing hint that points implicitly at the list/getById siblings. There is no explicit when-not guidance, no statement about defaults, and no indication of how to handle a zero result.

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