Skip to main content
Glama

processDefinition_activityStats

Retrieves activity-level statistics for a process definition, including instance counts per activity, failed job counts, and incident counts to support bottleneck analysis.

Instructions

Get activity-level statistics for a process definition: instance counts per activity, failed job counts, and incident counts. Useful for bottleneck analysis.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "processDefinition_activityStats"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
incidentsNo
failedJobsNo
incidentsForTypeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.3.0
    • addedInput schema / properties / failedJobs
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / incidents
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / incidentsForType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It adds useful context by listing the returned metrics (instance counts per activity, failed job counts, incident counts) and implying read-only access through 'Get,' but it does not state permissions, rate limits, response format, or whether the optional booleans alter the aggregation.

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?

The description is two sentences, front-loaded with the core operation and followed by a concise use case. Every sentence adds value without repetition or filler.

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 tool with four parameters, no annotations, and no output schema, the description does well to name the return metrics and use case. However, it leaves critical parameter semantics and behavioral details unexplained, so an agent would still need to inspect the schema and guess how the optional flags work.

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%, so the description must compensate for four undocumented parameters. It hints at the 'incidents' and 'failedJobs' booleans by mentioning incident counts and failed job counts, and 'for a process definition' implies the required id, but it never explains the 'incidentsForType' parameter or clarifies how the booleans affect the result.

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 uses a specific verb and resource: 'Get activity-level statistics for a process definition,' and names the metrics returned. It distinguishes itself from general process definition statistics by emphasizing activity-level and per-activity counts, though it does not explicitly name the sibling processDefinition_statistics it differs from.

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?

The phrase 'Useful for bottleneck analysis' gives an implied use case, which helps an agent understand when this tool might be appropriate. However, there is no explicit when-to-use guidance, no exclusions, and no direct comparison to sibling tools like processDefinition_statistics or processInstance_count.

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