Q a lot of talk about how many tools an LLM can support, whether or not, you know, you should give different tools, whether or not you should put all the tools in one MCP, which you guys also offer with the Composio MCP. Can you maybe give people Kind of state of the art today. Where do things go wrong? Uh, and maybe the slope of improvement of the models.
A Sure. So I think, uh, like we have seen over like a lot of practice that like more than like 20, 25, uh, actions like just confuses the server. Like it's not able to kind of like figure out which tool to use. And same goes with like, if the schema of the tools are really complex, that also confuses the agent. So we try to keep our kind of like schema simple. Like some of the things are like flattening the schemas, et cetera. In addition, I think, uh, Like basically I think it's like agents, like because they are LLMs inherently, so they like to think in natural language. So some of the things that we are planning on that front is like a single natural language execution of a tool so that like the agent does just gives like, like agent has just given a single tool and it can call any of the other kind of skills that we have like inside Composio with just natural language. So like create a notion doc and send a meeting invite just in natural language and we'll do that in the backend.
AI assessment note: “more than like 20, 25, actions like just confuses the server”