mcp server state persists across tool calls when it shouldn't - autogen 0.4.2

Hit this building a file search tool yesterday - the mcp server maintains state between tool calls even though each call should be stateless according to the spec. Reproduction: 1. Call mcp tool 'search_files' with query='test', returns 5 results 2. Call same tool with query='production', should return different results 3. Actual behavior: returns cached results from first call, doesn't execute the second query Tested on autogen 0.4.2 with mcp-typescript-sdk 1.0.3. The server's internal state from call 1 bleeds into call 2. Restarting the server between calls fixes it but that's not viable in production. Is this autogen's fault for not isolating server state, or is the mcp server supposed to handle this? The spec says tools should be stateless but doesn't specify who enforces that.