TeamShared

process_run_create

Create a Process run from a catalog process or a launchable playbook.

Board Pickup (process or playbook_slug=board-pickup) starts at Scan. Any playbook with tool_recipe.process_steps or a skill sequence can start a run without a hardcoded catalog entry. The run freezes playbook/skill versions + steps, current step, status, and stream_id=run:{id}. Human/gate steps open a Work item and link it. Not a Camunda / Zeebe / LangGraph workflow.

Input Schema

Name	Required	Description
`agent`	No	Override agent attribution label
`due_at`	No	Optional due date-time for the instance
`process`	No	Optional process slug or name (board-pickup / Board Pickup). Omit when playbook_slug names a launchable playbook.
`work_id`	No	Optional work UUID (writes WorkItem --case_of--> current ProcessStep)
`project_id`	No	Optional project UUID to bind this run (writes Project --runs--> Process)
`owner_agent`	No	Optional owner label for the instance
`playbook_slug`	No	Playbook to launch as a run. tool_recipe.process_steps storage the walk when present; otherwise the skill sequence is used. A playbook with a tool_recipe.process block, or a seed template slug such as claim, opens a long-running instance. Enough on its own — no catalog process required.
`subject_entity_id`	No	Optional ontology entity UUID the instance is about (a policyholder, a candidate). One entity can have many instances.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / playbook_slug / description

Previous value: -"Playbook to launch as a run. tool_recipe.process_steps drive the walk when present; otherwise the skill sequence is used. A playbook with a tool_recipe.process block, or a seed template slug such as claim, opens a long-running instance. Enough on its own — no catalog process required."New value: +"Playbook to launch as a run. tool_recipe.process_steps storage the walk when present; otherwise the skill sequence is used. A playbook with a tool_recipe.process block, or a seed template slug such as claim, opens a long-running instance. Enough on its own — no catalog process required."

Changed2 schema fields changedOct 19, 2026

changedInput schema / properties / playbook_slug / description

Previous value: -"Playbook to launch as a run. tool_recipe.process_steps drive the walk when present; otherwise the skill sequence is used. Enough on its own — no catalog process required."New value: +"Playbook to launch as a run. tool_recipe.process_steps drive the walk when present; otherwise the skill sequence is used. A playbook with a tool_recipe.process block, or a seed template slug such as claim, opens a long-running instance. Enough on its own — no catalog process required."

removedInput schema / properties / template

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Open an instance from a process template (e.g. claim). The template is frozen into the run, which starts in its first stage. Replaces process / playbook_slug."
-}

Changed4 schema fields changedOct 15, 2026

addedInput schema / properties / due_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional due date-time for the instance"
+}

addedInput schema / properties / owner_agent

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional owner label for the instance"
+}

addedInput schema / properties / subject_entity_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional ontology entity UUID the instance is about (a policyholder, a candidate). One entity can have many instances."
+}

addedInput schema / properties / template

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Open an instance from a process template (e.g. claim). The template is frozen into the run, which starts in its first stage. Replaces process / playbook_slug."
+}

Changed6 schema fields changedSep 15, 2026

changedInput schema / properties / playbook_slug / description

Previous value: -"Optional playbook whose tool_recipe.process_steps drive advancement (defaults to the process slug / catalog playbook)"New value: +"Playbook to launch as a run. tool_recipe.process_steps drive the walk when present; otherwise the skill sequence is used. Enough on its own — no catalog process required."

addedInput schema / properties / process / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / process / default
```
Added value: +null
```

changedInput schema / properties / process / description

Previous value: -"Process slug or name (board-pickup / Board Pickup)"New value: +"Optional process slug or name (board-pickup / Board Pickup). Omit when playbook_slug names a launchable playbook."

removedInput schema / properties / process / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "process"
-]
```

Changed3 schema fields changedSep 11, 2026

addedInput schema / properties / playbook_slug

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional playbook whose tool_recipe.process_steps drive advancement (defaults to the process slug / catalog playbook)"
+}

changedInput schema / properties / project_id / description

Previous value: -"Optional project UUID to bind this run"New value: +"Optional project UUID to bind this run (writes Project --runs--> Process)"

addedInput schema / properties / work_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional work UUID (writes WorkItem --case_of--> current ProcessStep)"
+}

AddedSep 10, 2026

TDQS

A3.7/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses that the run freezes playbook/skill versions, steps, current step and status, that stream_id is set to run:{id}, and that human/gate steps open and link a Work item. Missing are permission requirements, idempotency or duplicate-run behavior, and failure modes, which keeps this below a 5.

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?

The purpose is front-loaded in the first sentence and the remaining lines are dense, information-bearing statements about launching, freezing state, and Work item linking. Some jargon compounds (tool_recipe.process_steps, stream_id=run:{id}) and arbitrary line wrapping slightly hurt readability but nothing is filler.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and the description covers the create semantics, two sourcing paths, and the frozen-state side effects well. Given eight all-optional parameters and a long-running instance lifecycle, an agent would still lack guidance on what happens on invalid slugs or repeated creation, but the core is complete.

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 description coverage is 100%, so the schema already documents all eight optional parameters, and the baseline is 3. The description reinforces the process-vs-playbook_slug either/or ('Omit when playbook_slug names a launchable playbook', 'Enough on its own') and mentions the board-pickup slug, but that rule is already present in the schema text, so it adds little new meaning.

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?

The opening sentence gives a specific verb and resource ('Create a Process run') and names the two sourcing modes (catalog process or launchable playbook). The closing note 'Not a Camunda / Zeebe / LangGraph workflow' explicitly disambiguates it from external workflow engines, though it does not directly contrast with nearby siblings like agent_run_start or process_run_advance.

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 description explains that 'Board Pickup' starts at Scan and that any playbook with tool_recipe.process_steps or a skill sequence can start a run without a catalog entry, which implies when this tool applies. However, it never states when to choose process_run_create over process_run_advance, agent_run_start, or process_template, and offers no prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TeamShared tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

process_run_create

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources