Skip to main content
Glama

processDefinition_statistics

Retrieve instance, failed job, and incident counts for all deployed process definitions to monitor execution health and identify problematic workflows.

Instructions

Get process definition statistics across all deployed definitions: instance counts, failed job counts, and incident counts per definition.

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

Input Schema

NameRequiredDescriptionDefault
incidentsNo
failedJobsNo
rootIncidentsNo
incidentsForTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • addedInput schema / properties / failedJobs
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / incidents
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / incidentsForType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / rootIncidents
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/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 burden; it does disclose the returned aggregate dimensions and the important scope trait that results span ALL deployed definitions (no filtering or pagination mentioned). It omits whether the call is expensive on large deployments and how the optional flags change the response.

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 dense sentence with the verb and result fields front-loaded and no filler. It could have spent a few more words on the flags without harming structure, but nothing present is wasted.

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?

It covers what the tool returns, which partly substitutes for the missing output schema. However, for a tool whose four optional booleans materially change the result set, silence on those toggles leaves the definition short of complete for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for four optional booleans, so the description must compensate and largely does not. 'Failed job counts' and 'incident counts' loosely hint at failedJobs and incidents, but rootIncidents and incidentsForType are never explained, including whether these aggregates are on by default or off.

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?

Names a specific verb and resource ('Get process definition statistics') and enumerates the metrics returned: instance counts, failed job counts, incident counts. It does not distinguish itself from close siblings like processDefinition_count or processDefinition_activityStats, which an agent could easily confuse for these same aggregates.

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 gives no when-to-use guidance, no exclusions, and no pointer to alternative tools for narrower counts (e.g., processDefinition_count for a single total or activityStats for activity-level data). The agent must infer the use case entirely from the phrase 'across all deployed definitions'.

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