mcp 0.5.0 - tools can't declare dependencies, agent schedules them wrong and everything breaks
ok so we have a workflow where tool A fetches data, tool B processes it, tool C writes results. in 0.5.0 there's no way to declare that B depends on A's output or C depends on B's output. agent schedules them nondeterministically, sometimes C runs before B finishes, sometimes B runs before A returns data. entire workflow just fails randomly. we've been working around it by having each tool poll for its dependencies in a retry loop which is completely insane and burns through our api quota. does anyone know if there's a way to declare tool dependencies in 0.5.0 or do we just have to manually coordinate execution order in the agent prompt
hit this building a data pipeline. tool B needs tool A output, agent schedules them in parallel.
we hit this building an etl pipeline last week. tool B needs output from tool A, agent scheduled them in parallel, everything failed. added explicit dependency declarations in our wrapper but the sdk itself has no concept of tool dependencies. how are people handling multi-step workflows where order matters?