> Streaming would make sense if I were piping large sample arrays directly, but those get aggregated server-side before returning thitami's point on perceived

> Streaming would make sense if I were piping large sample arrays directly, but those get aggregated server-side before returning thitami's point on perceived latency is the thing I'd still watch. had the same "its fine, its fast enough" moment in a different MCP context (iOS simulator automation)... turned out the 300ms per-tool-call was what made the whole loop feel sluggish even though each individual query was "fast". got it down to ~20ms and Claude felt noticeably less hesitant between calls after that. cant fully explain why but the behavior shift was real. probably not your problem at 90 rows of scalar data =) just a thing I wish I had clocked earlier.