logoalt Hacker News

asdev07/31/20254 repliesview on HN

I feel like tool calling killed RAG, however you have less control over how the retrieved data is injected in the context.


Replies

billmalarky07/31/2025

Search tool calling is RAG. Maybe we should call it a "RAG Agent" to be more en vogue heh. But RAG is not just similarity search on embeddings in vector DBs. RAG is any type of a retrieval + context injection step prior to inference.

Heck, the RAG Agent could run cosign diff on your vector db in addition to grep, FTS queries, KB api calls, whatever, to do wide recall (candidate generation) then rerank (relevance prioritization) all the results.

You are probably correct that for most use cases search tool calling makes more practical sense than embeddings similarity search to power RAG.

show 1 reply
OutOfHere07/31/2025

How would you use tool-calling to filter through millions of documents? You need some search functionality, whether old-school search or embedding search. If you have only thousands of documents, then sure, you don't need search, as you can feed them all to the LLM.

show 2 replies
gnulinux08/01/2025

Tool calling complements RAG. You build a full scale RAG (embedding, reranker, create prompt, get output from LLM) and hook that to a tool another agent can see. That combines both their power.