Hey, yes it's on the same family for sure! The difference is that it works with anything, not just MCPs, and it runs in-process without any additional infra (which usually isn't the case for other RAG solutions). Happy to hear your feedback if you try it out :)
This is neat! It tackles a boring but real problem with agents. When you have too many tools, the model gets confused. This is a good search box for its tools instead of dumping everything into the prompt. Benchmarks is amazing!
really cool, first time I've seen anyone treat "which tools does my agent even get to see" as its own problem. Is the roadmap more about pushing deeper on the retrieval side over time, or mostly about covering more frameworks/languages?
Thank you! Right now we're adding some frameworks adapters to lower the adoption friction, and pushing deeper on new algorithms on the retrieval side. More languages support is not on the radar yet, but we accept contributions! :)
Yes! I should have mentioned in the original post. It was actually built in Typescript at first, but then the performance were not good enough for production use cases. With Rust the footprint was way lower, and we managed tear the latency down from 200ms to 20ms for a single search
Would love to hear your feedback if you can try it. We initially rolled out BM25 for tool search as it worked best for us internally. Recently rolled out also embeddings and an hybrid option that is being tested in production as we speak
Hey guys, fair callout, but no AI involved, promise! You're right that some comments look off and someone's farming karma for sure. We see genuine traffic to the repo anyway, so people is checking it out!
Critical feedback is what we're here for, so fire away if you have anything :)
This comment was detected by our software as AI generated. It could always be a false positive, but if you're using AI at all to write your comments, please stop. It's against the guidelines and only harms your reputation in the eyes of the community.
Isn't this just RAG for tools? Also, MCP already has tool search, how is this useful in that case?
Hey, yes it's on the same family for sure! The difference is that it works with anything, not just MCPs, and it runs in-process without any additional infra (which usually isn't the case for other RAG solutions). Happy to hear your feedback if you try it out :)
[stub for offtopicness]
This is neat! It tackles a boring but real problem with agents. When you have too many tools, the model gets confused. This is a good search box for its tools instead of dumping everything into the prompt. Benchmarks is amazing!
Thank you! Let us know how it works if you try it out :) of course real world is another story, but we agree benchmarks are amazing indeed!
really cool, first time I've seen anyone treat "which tools does my agent even get to see" as its own problem. Is the roadmap more about pushing deeper on the retrieval side over time, or mostly about covering more frameworks/languages?
Thank you! Right now we're adding some frameworks adapters to lower the adoption friction, and pushing deeper on new algorithms on the retrieval side. More languages support is not on the radar yet, but we accept contributions! :)
Benchmarks looks very promising! I’ll try to test this new tool in the next few days thanks for sharing!
Thank you mate! Please share your feedback :)
This looks so nice!
I see you built the core in Rust with bindings to TS/Python. y?
Yes! I should have mentioned in the original post. It was actually built in Typescript at first, but then the performance were not good enough for production use cases. With Rust the footprint was way lower, and we managed tear the latency down from 200ms to 20ms for a single search
man this could save me so much money lol
Would love to hear your feedback if you can try it. We initially rolled out BM25 for tool search as it worked best for us internally. Recently rolled out also embeddings and an hybrid option that is being tested in production as we speak
[flagged]
[dead]
Anyone else suspect this is an entirely astroturfed comment section?
Yes. The comments read like positive ai vibes and their profiles seem empty and low karma.
Hey guys, fair callout, but no AI involved, promise! You're right that some comments look off and someone's farming karma for sure. We see genuine traffic to the repo anyway, so people is checking it out!
Critical feedback is what we're here for, so fire away if you have anything :)
This comment was detected by our software as AI generated. It could always be a false positive, but if you're using AI at all to write your comments, please stop. It's against the guidelines and only harms your reputation in the eyes of the community.