Architecture Decision for many Tools
Wanted to ASK what you would recommend for a Agent that has possible either
1.many Tools (20+)
2. Or 1 Tool that can Take a Type a Input
Toolxyz(inputdata)
Vs
Toolxyz(Type,inputdata)
Iam debating whats better.. Like the many Tools would have less need for a System prompt
While the 1 Tool would need a bigger one ? To make AI aware of the types ?
Like what would you recommend for Mastra aproach ?? @roamin
Basically want to build a Agent that can build different Blocks that Output json .. and there are Like potentially a growing number. And i feel Like the model will eventually be overwhelmed by amount of Tools or types ? Any advise ;)?
4 Replies
š Created GitHub issue: https://github.com/mastra-ai/mastra/issues/10522
š If you're experiencing an error, please provide a minimal reproducible example whenever possible to help us resolve it quickly.
š Thank you for helping us improve Mastra!
Hi! This a common question we get asked but the answer is it depends.
Different options:
1. agent with many tools
2. Routing agent delegating to sub agents with subselection of tools
3. Having a tool router (like you described) that first searches the tool or configures it dynamically
It depends on your app!
ahh ok. iam already aware of the options . but i guess what iam asking which of these is best for the agent to handle the most amount of different scenarios . like which one would you pick if you would need to support llike 30+ different tool or type scenarios ? or doesnt it matter ? from your experience ?
Tool router sound nice idea ? btu then you would need inital tool call to get tools ? hmm sounds like a good idea to keep the intal system prompt smaller . will need to think about that
Iam guessing i possibly grow from 20 to 50 differnt blocks maybe
Tool Router seems the best idea for large tool lists.
Anthropic released tool search which leads me to believve they think that way too