Back to Feed
Agents / Benchmarks & Evals

Interpretable Agentic Retrieval for Complex Documents

Original: Beyond Top-K: Replacing Black-Box Retrieval with Interpretable Agentic Operations

Listen to the summary

Uses a voice available on your device

Audio options
On this page

Key Takeaways

  • Replaced black-box retrieval pipelines with an interpretable, agentic system called Read (Reliable Embedding-free Agentic Document-search).
  • Introduced a table-aware chunker that reduced unitless numeric chunks from 18.0% down to 0.3% when using 2,000-character chunks.
  • Outperformed a dense baseline by 23.5 points in accuracy for structured document queries.
  • Utilized a Model Context Protocol server to allow agents to perform specific operations like lexical search, outline navigation, and line-range reads.

Summary & Methodology Analysis

The researchers replaced traditional chunk-and-embed retrieval with Read, a Model Context Protocol server that enables deterministic agentic operations. This approach addresses the failures of dense embedding models, which often lose layout-dependent context such as fiscal-year headers or units when breaking text into chunks. By implementing a table-aware chunker, the system propagates these critical headers across document boundaries, significantly increasing the reliability of numeric data retrieval. The agentic loop follows a cycle of hypothesis, search, outline-based inspection, and specific line-range reads, concluding with arithmetic calculation and mechanical verification of groundedness against the raw text. Performance testing on the Gujarat Finance Accounts 2024-25, Volume I showed that while a dense baseline with 2,000-character chunks and k=16 achieved 35.3% accuracy, the Read system exceeded this by 23.5 percentage points. The table-aware chunker proved highly effective, reducing the prevalence of unitless numeric chunks from 18.0% to 0.3% at the same chunk scale. The study highlights that the performance of the system relies on the specific PDF-to-Markdown converter employed, as conversion artifacts can impact results. Limitations include the reliance on a single financial document and one backbone model, namely gemini-2.5-pro, meaning results may not generalize across different domains or model architectures. Furthermore, the benchmark is small, consisting of only 51 questions, which prevents definitive statistical resolution when comparing Read against other methods like BM25.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the core problem this paper solves?

Traditional retrieval systems based on embeddings frequently fail on structured documents like financial reports because they destroy important layout-dependent meaning.

Q2. What is the Read system?

Read stands for Reliable Embedding-free Agentic Document-search, and it functions as a read-only Model Context Protocol server.

Q3. Does this system improve retrieval accuracy?

Yes, it outperformed a dense baseline by 23.5 percentage points in accuracy.

Q4. What specific agentic operations are used?

The system uses normalized lexical search (grep), structural navigation (outline), and bounded span reads (read).

Q5. How does the system handle units in tables?

It uses a table-aware chunker that propagates unit and fiscal-year headers across document boundaries.

Q6. What models and datasets were involved?

The study used the Gujarat Finance Accounts 2024-25, Volume I dataset and the gemini-2.5-pro model.

Q7. How is groundedness verified?

The system performs mechanical validation by verifying that every answer figure exists verbatim within the retrieved text.

Q8. Are there limitations regarding the dataset size?

Yes, the benchmark size is small at only 51 questions, leaving some performance comparisons statistically unresolved.

Q9. Does the system rely on standard embedding models?

It uses embedding-free operations, although the researchers compared it against baselines using bge-base-en-v1.5 and ms-marco-MiniLM-L-6-v2.