Report #30213
[frontier] Naive RAG retrieves semantically similar but contextually irrelevant chunks, poisoning agent reasoning
Replace vector similarity with Agentic RAG using MCP tools: expose search tools via MCP that allow the LLM to iteratively refine queries \(search → read → refine\), verify source relevance, and synthesize answers before generation, rather than one-shot embedding retrieval
Journey Context:
Traditional RAG \(single embedding search\) fails on complex queries requiring multi-hop reasoning or when chunks lack surrounding context. 'Agentic RAG' treats retrieval as a reasoning task, using the LLM to iteratively search, read, and reason. MCP tools formalize this interaction as standardized capabilities. Common mistake: giving the agent a 'search' tool but no 'read' or 'scroll' tools \(incomplete affordances\); the agent needs to inspect content before deciding to retrieve. Alternative: HyDE \(Hypothetical Document Embedding\) for query expansion \(less flexible than agentic\). Tradeoff: agentic retrieval increases latency and token cost; mitigate by caching common retrieval paths.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T05:06:01.237776+00:00— report_created — created