In production, MCP can struggle with tools that return long responses: fetching 100 Gmail emails may overwhelm context and leave developers unable to post-process the output before it reaches the final application.

“The first answer like how MCB could be but so some of the limitations that we've been observing in production is like MCB, let's just say you have a tool that has really long context,”

“really long set of response.”

“Currently if you use MCB for those kind of tools,”

“it ends up sort of messing up, right? Because let's say I'm trying to fetch like 100 emails on Gmail.”

“and my sort of context over blockers and I'm not able to sort of post process the output that is coming out from MCP, I'm not able to sort of play around with it before it reaches my sort of final lab and a lot of like potential failure scenarios like that exist. Some of the other things that we have observed is like hey maybe I want to sort of change the tool descriptions but like in MCP the tool descriptions are controlled by the server itself and so essentially for me as a developer who's sort of”