Have you ever felt confused and overwhelmed with the number of choices of tools to build your agent? I kept facing this problem and built ToolsForAgent to provide personalized recommendations for frameworks, LLM providers, vector databases, and more. I hope you find it useful as well.
Hello everyone! 👋
I'm Vidushee, and I'm excited to share ToolsForAgent with you.
If you've ever wanted to build an AI agent but didn't know which tools to use, this is for you. Just describe what you want your agent to do, and it'll suggest a curated list of tools with descriptions and direct links.
Why I built this:
I kept facing this problem: "I have an idea for an agent, but what tools should I actually use?". With ToolsForAgent, I wanted to make that discovery instant and intelligent.
I'd love to hear your thoughts! Have you built an AI agent before? What tools did you wish you'd known about earlier? Please share your feedback below! 🚀
Report
Interesting. Surprised why the LLM Provider is only showing OpenAI while leaving out Gemini, Claude and others.
For Observability, I can see “Weights and Biases Traces” in one prompts and “Langsmith” for another. Would be helpful to call out the rationale for suggesting one tool over the other.
You could add more context for your recommendations as
1. Context-aware filtering
2. Startup vs enterprise
3. Solo dev vs team
4. Cost-sensitive vs performance-first
5. Regulated vs experimental
Opinionated tradeoffs
1. “Use FAISS if X, Pinecone if Y”
2. “Use framework Z if latency matters”
Happy to review once you implement some of these points.
Very useful. I'm building an agent that generates workflow automation and it suggested tools I was already using but also gave me 2 new tools I wasn't aware of!
@vidushee_geetam, This is interesting. Picking the agent stack usually takes longer than building the agent itself, and the one-tool-per-category approach genuinely reduces overthinking. Curious to see how it handles more complex agent setups.
Observer
Interesting. Surprised why the LLM Provider is only showing OpenAI while leaving out Gemini, Claude and others.
For Observability, I can see “Weights and Biases Traces” in one prompts and “Langsmith” for another. Would be helpful to call out the rationale for suggesting one tool over the other.
You could add more context for your recommendations as
1. Context-aware filtering
2. Startup vs enterprise
3. Solo dev vs team
4. Cost-sensitive vs performance-first
5. Regulated vs experimental
Opinionated tradeoffs
1. “Use FAISS if X, Pinecone if Y”
2. “Use framework Z if latency matters”
Happy to review once you implement some of these points.
Observer
@vijender_p Thank so much for trying it out and for providing valuable feedback. Will implement these improvements in the next release.
Observer
@aditya_challa Thank you for trying out my tool. Sure, I can add that feature.
Does It Exist
Very useful. I'm building an agent that generates workflow automation and it suggested tools I was already using but also gave me 2 new tools I wasn't aware of!
Observer
@prabhjotsl Thank you for trying it out. Glad you found it useful :)
Does It Exist
@vidushee_geetam would be next level, if you could also show tools that agents can use as well, would save a lot of time researching those.
Observer
@prabhjotsl Noted. Thanks! Will add this to the next version.
QApilot
@vidushee_geetam, This is interesting. Picking the agent stack usually takes longer than building the agent itself, and the one-tool-per-category approach genuinely reduces overthinking. Curious to see how it handles more complex agent setups.