go-sdk

Describe the bug When you call a tool with an argument field that's not in the input schema, it returns a jsonrpc "error" message instead of a result with so the client LLM can see it. To Reproduce Steps to reproduce the behavior: 1. Call any tool with an invalid argument. 2. Check the result error. It looks something like this: Expected behavior** I expected to see an error something like this:

Issue Title MCP Server Multi-Instance Deployment: Session sharing issue across load balancer backend servers Description When deploying MCP server with multiple backend instances behind a load balancer, sessions are not properly shared across different server instances, causing "session not found" errors. Problem Details After scaling the MCP server from a single instance to multiple instances (3 RS - Real Servers), clients experience intermittent "session not found" errors when trying to reuse session IDs obtained from previous requests. Root Cause Analysis Single Instance (Previous): All requests went to the same backend server, so session IDs were valid across the entire session lifecycle Multiple Instances (Current): Load balancer, not use session strick