mcp 0.5.0 - tool execution order is nondeterministic when multiple tools ready
hit this building our internal workflow system last week. when multiple tools are ready to execute (dependencies satisfied, no blocking), the sdk picks execution order nondeterministically. tested with tools A, B, C all ready at same time. across 10 runs got execution orders: ABC, ACB, BAC, CBA, ABC, BAC, ABC, CAB, ACB, BAC. this breaks workflows that assume implicit ordering. we had to add explicit dependency chains even when tools don't actually depend on each other, just to get deterministic execution. sdk 0.5.0, running on node 20.11.0. anyone else seeing this?
hit this yesterday. same tool dependency DAG, execution order changes between runs. need deterministic scheduling or at least a seed param
ok so we hit this exact thing last month and it killed a 9 hour batch job because tool execution order changed between dev and prod. same DAG, same inputs, completely different results. ended up having to add explicit ordering constraints in tool definitions which feels like a hack