Skip to main content
Glama

processDefinition_list

List deployed process definitions and filter by key, name, version, category, tenant, or status to retrieve IDs, versions, and deployment details.

Instructions

List deployed process definitions. Filter by key, name, version, category, or tenant. Returns key, id, version, and deployment info for each 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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNo
nameNo
activeNo
keysInNo
sortByNo
keyLikeNo
versionNo
categoryNo
nameLikeNo
sortOrderNo
suspendedNo
deployedAtNo
incidentIdNo
maxResultsNo
tenantIdInNo
versionTagNo
firstResultNo
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. Changed36 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 / firstResult
      Added value: +{
      +  "type": "number"
      +}
    • 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 / maxResults
      Added value: +{
      +  "type": "number"
      +}
    • 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 / sortBy
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sortOrder
      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

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 behavioral burden. It discloses the return field set ('key, id, version, and deployment info'), which is useful, but says nothing about pagination, default ordering, or result limits despite 36 parameters including maxResults/firstResult/sortBy.

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 with the purpose front-loaded, then filters, then return shape. No wasted wording, though the brevity is partly under-specification given the parameter count.

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 36-parameter list tool with no annotations and no output schema, the description is far too thin. It should at minimum explain pagination, sorting, and the Like/tenant variants, none of which are covered.

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?

36 parameters with 0% schema description coverage, and the description only maps five of them (key, name, version, category, tenant). The remaining ~31, including pagination, sorting, Like-variants, and tenant flags, are undocumented anywhere, so the description fails to compensate for the coverage gap.

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 ('List deployed process definitions') that clearly reads as a query operation. It does not, however, distinguish itself from siblings like processDefinition_count, processDefinition_statistics, or processDefinition_getById, leaving the agent to infer the boundary.

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?

It names the filter dimensions (key, name, version, category, tenant), which implies the query use case, but never says when to prefer this over count/statistics/get or when it should not be used. Guidance is only implicit.

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