Skip to main content
Glama

task_count

Count user tasks matching filter criteria for workload sizing and planning. Supports filtering by assignee, due date, priority, and other task attributes.

Instructions

Count user tasks matching filter criteria. Supports same filters as task list. Useful for workload sizing.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
ownerNo
activeNo
taskIdNo
dueDateNo
assignedNo
assigneeNo
dueAfterNo
nameLikeNo
priorityNo
taskIdInNo
createdOnNo
dueBeforeNo
suspendedNo
assigneeInNo
tenantIdInNo
unassignedNo
descriptionNo
executionIdNo
maxPriorityNo
minPriorityNo
nameNotLikeNo
assigneeLikeNo
createdAfterNo
followUpDateNo
involvedUserNo
nameNotEqualNo
parentTaskIdNo
updatedAfterNo
assigneeNotInNo
candidateUserNo
createdBeforeNo
followUpAfterNo
taskVariablesNo
candidateGroupNo
caseInstanceIdNo
followUpBeforeNo
withoutDueDateNo
candidateGroupsNo
caseExecutionIdNo
delegationStateNo
descriptionLikeNo
ownerExpressionNo
withoutTenantIdNo
caseDefinitionIdNo
processVariablesNo
caseDefinitionKeyNo
dueDateExpressionNo
processInstanceIdNo
taskDefinitionKeyNo
assigneeExpressionNo
candidateGroupLikeNo
caseDefinitionNameNo
dueAfterExpressionNo
withCandidateUsersNo
createdOnExpressionNo
dueBeforeExpressionNo
processDefinitionIdNo
processInstanceIdInNo
taskDefinitionKeyInNo
withCandidateGroupsNo
activityInstanceIdInNo
includeAssignedTasksNo
processDefinitionKeyNo
caseInstanceVariablesNo
processDefinitionNameNo
taskDefinitionKeyLikeNo
withoutCandidateUsersNo
assigneeLikeExpressionNo
caseDefinitionNameLikeNo
createdAfterExpressionNo
followUpDateExpressionNo
involvedUserExpressionNo
processDefinitionKeyInNo
taskDefinitionKeyNotInNo
updatedAfterExpressionNo
withoutCandidateGroupsNo
candidateUserExpressionNo
caseInstanceBusinessKeyNo
createdBeforeExpressionNo
followUpAfterExpressionNo
variableNamesIgnoreCaseNo
candidateGroupExpressionNo
followUpBeforeExpressionNo
variableValuesIgnoreCaseNo
candidateGroupsExpressionNo
processDefinitionNameLikeNo
withCommentAttachmentInfoNo
withTaskVariablesInReturnNo
processInstanceBusinessKeyNo
caseInstanceBusinessKeyLikeNo
followUpBeforeOrNotExistentNo
processInstanceBusinessKeyInNo
processInstanceBusinessKeyLikeNo
withTaskLocalVariablesInReturnNo
processInstanceBusinessKeyExpressionNo
followUpBeforeOrNotExistentExpressionNo
processInstanceBusinessKeyLikeExpressionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed98 schema fields changedv1.3.0
    • addedInput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / activityInstanceIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigned
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / assignee
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigneeExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigneeIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigneeLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigneeLikeExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / assigneeNotIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateGroup
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateGroupExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateGroupLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateGroups
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateGroupsExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateUser
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / candidateUserExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseDefinitionNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseExecutionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseInstanceBusinessKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseInstanceBusinessKeyLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / caseInstanceVariables
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createdAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createdAfterExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createdBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createdBeforeExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createdOn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / createdOnExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / delegationState
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / descriptionLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueAfterExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueBeforeExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / dueDateExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / executionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpAfterExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpBefore
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpBeforeExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpBeforeOrNotExistent
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpBeforeOrNotExistentExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpDate
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / followUpDateExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / includeAssignedTasks
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / involvedUser
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / involvedUserExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / maxPriority
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / minPriority
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameNotEqual
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameNotLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / owner
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / ownerExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / parentTaskId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / priority
      Added value: +{
      +  "type": "number"
      +}
    • 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 / processDefinitionName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKeyExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKeyIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKeyLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceBusinessKeyLikeExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processInstanceIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processVariables
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / suspended
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / taskDefinitionKey
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDefinitionKeyIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDefinitionKeyLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskDefinitionKeyNotIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / taskVariables
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / unassigned
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / updatedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / updatedAfterExpression
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / variableNamesIgnoreCase
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / variableValuesIgnoreCase
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withCandidateGroups
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withCandidateUsers
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withCommentAttachmentInfo
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withTaskLocalVariablesInReturn
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withTaskVariablesInReturn
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutCandidateGroups
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutCandidateUsers
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutDueDate
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a read-only aggregate but does not state that the result is a bare count rather than a task collection, whether the count respects pagination or is an exhaustive total, or whether large filter sets make it expensive. For a tool with no annotations and no output schema, these omissions matter.

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?

Three short sentences, front-loaded with the action and with no filler. The brevity is a virtue in form even though the content under-delivers given the schema's size.

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?

A 98-parameter tool with zero schema description coverage, no annotations, and no output schema needs a substantially richer description than three sentences. Critically, it never says what is returned (presumably a numeric total), which matters precisely because there is no output schema to explain it.

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 schema has 98 parameters at 0% description coverage, so the description must compensate and it does not. 'Supports same filters as task list' defers all per-parameter meaning to another tool's documentation, leaving an agent to guess at the many near-duplicate fields (assignee vs assigneeIn vs assigneeLike vs assigneeExpression) with no guidance.

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 user tasks matching filter criteria'), which distinguishes it from the listing siblings like task_list and history_listTaskInstances. It stops short of naming those siblings explicitly, but the count-vs-list distinction is legible from the text alone.

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?

'Useful for workload sizing' gives one concrete scenario and 'Supports same filters as task list' implies task_list is the related alternative. However, it never says when to prefer this over task_list (e.g., when you only need the total, not the rows), which is the single decision an agent actually faces here.

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