17 pointsby jack16893 hours ago3 comments
  • vinci00an hour ago
    Isn't this just RAG for tools? Also, MCP already has tool search, how is this useful in that case?
    • jack1689an hour ago
      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 :)
  • tomhowan hour ago
    [stub for offtopicness]
    • missmoss2 hours ago
      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!
      • jack16892 hours ago
        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!
    • flaviobernoni2 hours ago
      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?
      • jack16892 hours ago
        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! :)
    • KristianLentino3 hours ago
      Benchmarks looks very promising! I’ll try to test this new tool in the next few days thanks for sharing!
      • rstagi3 hours ago
        Thank you mate! Please share your feedback :)
    • atenareply2 hours ago
      This looks so nice!
      • atenareply2 hours ago
        I see you built the core in Rust with bindings to TS/Python. y?
        • jack16892 hours ago
          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
    • iustinai3 hours ago
      man this could save me so much money lol
      • jack16893 hours ago
        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
    • panpotan hour ago
      [dead]
    • kenlo2 hours ago
      [flagged]
  • bbg24012 hours ago
    Anyone else suspect this is an entirely astroturfed comment section?
    • tortillaan hour ago
      Yes. The comments read like positive ai vibes and their profiles seem empty and low karma.