Most MCP demos are one tool call. Real work is a dependency chain: create a project, read its ID, pass that ID into the next operation, and keep going.
The costly part is often the handoff. In the benchmark's ecommerce workflow, both configurations passed the same five verifier checks and created the same deliverables. Tura Direct used 3 model requests instead of 11, and 56,372 total tokens instead of 262,915 (78.6% lower), despite making 11 MCP calls rather than 9. The saving is repeated model context, not skipped work.
Tura's command_run Macro lets an agent describe the dependency graph once. Values from a successful step can be used by later steps, while independent commands run together. The model does not need a new turn just to read an ID and copy it into the next tool call.
For longer chains, each handoff kept inside the Macro can avoid another model re-entry, so repeated-context savings can accumulate. That is not a universal linear law—caching, retries, and workflow shape still matter—but it is a useful lever for multi-step MCP work.
Full trace, caveats, and variable inheritance: https://turaai.net/blog#what-we-learned-from-the-mcp-workflow-benchmark
Source code: https://github.com/Tura-AI/tura
Disclosure: I am sharing work from Tura-AI.
