Skip to main content
Glama

processDefinition_count

Count deployed process definitions matching specified filter criteria so you can plan pagination before listing results.

Instructions

Count deployed process definitions matching filter criteria. Supports same filters as list. Use before listing to plan pagination.

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

Input Schema

NameRequiredDescriptionDefault
keyNo
nameNo
activeNo
keysInNo
keyLikeNo
versionNo
categoryNo
nameLikeNo
suspendedNo
deployedAtNo
incidentIdNo
tenantIdInNo
versionTagNo
startableByNo
categoryLikeNo
deploymentIdNo
incidentTypeNo
resourceNameNo
deployedAfterNo
latestVersionNo
versionTagLikeNo
incidentMessageNo
withoutTenantIdNo
resourceNameLikeNo
withoutVersionTagNo
incidentMessageLikeNo
processDefinitionIdNo
startableInTasklistNo
processDefinitionIdInNo
notStartableInTasklistNo
startablePermissionCheckNo
includeProcessDefinitionsWithoutTenantIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed32 schema fields changedv1.3.0
    • addedInput schema / properties / active
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / categoryLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deployedAfter
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deployedAt
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / deploymentId
      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 / incidentType
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / includeProcessDefinitionsWithoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / key
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / keyLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / keysIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / latestVersion
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / nameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / notStartableInTasklist
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / processDefinitionId
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / processDefinitionIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / resourceName
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / resourceNameLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / startableBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / startableInTasklist
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / startablePermissionCheck
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / suspended
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / tenantIdIn
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / version
      Added value: +{
      +  "type": "number"
      +}
    • addedInput schema / properties / versionTag
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / versionTagLike
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / withoutTenantId
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / withoutVersionTag
      Added value: +{
      +  "type": "boolean"
      +}
  2. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry the behavioral burden. "Count" implies a read-only, non-destructive operation and "supports the same filters as list" documents filter-semantics parity, but it says nothing about the return shape (a single integer), authorization-based filtering, or cost against large datasets.

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?

Three short sentences, front-loaded with the action and scope, then immediate usage guidance. No filler, no repetition of the tool name, and nothing could be removed without losing information.

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 32 undocumented parameters, no annotations, and no output schema, the definition is thin. An agent would still need to open the sibling list tool or guess at filter semantics and would have no idea that the response is a bare count value.

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?

There are 32 parameters with 0% schema description coverage, so the description must compensate and largely does not. "Supports same filters as list" is the only parameter guidance and it merely redirects the reader to a sibling tool rather than explaining any of the key/name/like/tenant/incident filter families.

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?

"Count deployed process definitions matching filter criteria" gives a specific verb (count) and resource (process definitions), and the second sentence explicitly positions it relative to processDefinition_list. It stops short of 5 only because it doesn't distinguish from other aggregate-oriented siblings such as processDefinition_statistics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use before listing to plan pagination" gives a concrete triggering condition and implies the alternative (list) without reading another schema. There is no explicit when-not guidance or note about when a direct list call would be preferable for small result sets.

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