writing-workflow-pseudocode

You can embed tool calls directly into workflow pseudocode by integrating execution details into do steps, eliminating the need for a separate tool-call table. This approach merges workflow structure and tool execution details into a single document.

Documenting REST and Bash calls in workflow pseudocode requires using via clauses with explicit tool types. This inline notation captures tool execution details directly within the workflow steps, supporting batching and substep nesting.

Yes, inline tool calls support workflows involving MCP, REST, Bash, File, and LLM calls. You can document mixed tool usage and batch notation like x12 or x6 par directly within the pseudocode steps.

You designate pure steps in workflow pseudocode by omitting the via clause. This approach distinguishes steps that do not involve tool execution from those with inline MCP, REST, Bash, File, or LLM calls.

Inline workflow pseudocode supports batching with notation like x12 or x6 par and substep nesting. Substep nesting allows you to document complex multi-tool segments with their own tool usage references within a single merged artifact.

Using inline tool calls eliminates the need for a separate tool-call table by merging artifacts. This approach captures both workflow structure and tool execution details in a single document, reducing documentation fragmentation and improving readability.