Skip to main content
Glama

history_listActivityInstances

Query historic activity instances for a process instance to retrieve activity ID, name, type, start and end times, duration, and user-task assignee.

Instructions

Query historic activity instances for a process instance. Returns activityId, name, type, startTime, endTime, duration, and assignee for user tasks.

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

Input Schema

NameRequiredDescriptionDefault
sortByNo
canceledNo
finishedNo
sortOrderNo
activityIdNo
maxResultsNo
tenantIdInNo
unfinishedNo
executionIdNo
firstResultNo
activityNameNo
activityTypeNo
startedAfterNo
taskAssigneeNo
completeScopeNo
finishedAfterNo
startedBeforeNo
finishedBeforeNo
withoutTenantIdNo
processInstanceIdNo
activityInstanceIdNo
processDefinitionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changedv1.3.0
    • addedInput schema / properties / activityId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / activityInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / activityName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / activityType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / canceled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / completeScope
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / finished
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / finishedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / finishedBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / startedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / startedBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskAssignee
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / unfinished
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  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?

No annotations are supplied, so the description carries the full burden, and it discloses only the returned fields. It omits pagination behavior for maxResults/firstResult, default sort behavior, whether historic data depends on the process engine's history level being enabled, and what the finished/unfinished/canceled flags actually mean for results.

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?

Two short, front-loaded sentences with no filler and an efficient statement of the return shape. It is arguably under-specified for a 22-parameter tool, but that is a completeness issue rather than verbosity.

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 22-parameter query with zero schema descriptions, no annotations, and no output schema, the definition is far too thin. The return-field list partly substitutes for the missing output schema, but it leaves the agent without enough information to use most filters or pagination 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 22 parameters, so the description must compensate and largely fails to do so. It only implies processInstanceId scoping and lists some return fields; it adds no meaning for sortBy, sortOrder, tenant filters, activityType, completeScope, or the several date-range parameters.

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 (query historic activity instances) and a scope (process instance), clearly distinct from siblings like history_listProcessInstances and history_listTaskInstances. It stops short of naming alternatives, so it is clear but not fully differentiated by routing language.

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?

No explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only implied by 'for a process instance', which says nothing about choosing between this and history_listTaskInstances or when the various finishing/cancellation filters should apply.

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