Skip to main content
Glama

processDefinition_getCalledProcesses

List all process definitions statically called via call activity by a given process definition ID to analyze dependencies.

Instructions

List all process definitions statically called (via call activity) by a given process definition ID. Useful for dependency 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_getCalledProcesses"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does add the meaningful qualifier that calls are 'static' (call-activity based) rather than runtime-invoked. However, it says nothing about whether results are transitive/recursive, whether only deployed definitions are included, or whether the operation is read-only.

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?

Two short sentences, front-loaded with the operation and scope, then a brief use-case rationale. No filler or duplication.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required param, no nesting, no annotations), but there is no output schema, and the description does not say what the returned 'process definitions' contain — full objects vs. identifiers only. That gap matters for an agent deciding whether a follow-up getById call is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the single 'id' parameter has no schema description. The description partially compensates by clarifying the id is a process definition ID (not a key), which is important given siblings that take keys, but it does not state accepted formats or whether an invalid/missing ID errors or returns empty.

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 all process definitions statically called (via call activity) by a given process definition ID' — which is clearly distinct from siblings like getById or getXmlById. It does not explicitly name an alternative, but the resource and relationship it exposes are unambiguous.

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 dependency analysis' implies a use case but gives no when-to-use/when-not criteria, no alternatives, and no prerequisites. An agent knows roughly why it would call this, but not when another sibling would be preferable.

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