mcp sdk 0.5.0 - can you pass context from one tool execution to next tool or is state completely isolated
I am testing tool chains where tool B needs output from tool A, but I cannot find in documentation if execution context persists between tool calls or if each tool starts with clean state. Does anyone know if there is mechanism to pass state forward, or do I need to build wrapper that holds context externally?
need this badly for multi-user agents. context object would be perfect but guessing 0.5.0 doesn't have it?
we need this for multi-step workflows where tool B needs data from tool A's execution. right now we're serializing state into tool output and parsing it in the next tool which is ugly and brittle. does 0.5.0 support any kind of context passing between tools?
we built a context object that persists across tool calls in our fork of 0.5.0. basically just a dict that gets passed to every tool's execution env. ugly but works for simple state sharing