# Max Docs: the hard ceiling on what reaches the model > Max Docs caps how many sources reach the LLM per call — protecting answer quality and cost from context overload. **Category:** Retrieval Grounding **Author:** NeuralSeek Team · **Published:** June 9, 2026 **Canonical:** https://neuralseek.ai/ai-grounded/max-docs **Section index:** https://neuralseek.ai/ai-grounded More context is not always better, and treating it as though it were is one of the most expensive mistakes in production AI. Stuff too many documents into a single call and three things go wrong at once: the model loses the thread as the signal-to-noise ratio collapses, latency climbs as it wades through more text, and the bill grows with every extra token. Max Docs sets a hard ceiling on how many sources reach the model per request, forcing the system to send only its strongest matches. ## What it actually does After retrieval ranks the candidate documents, Max Docs keeps the top N and discards the rest before anything reaches the model. It is a deliberate constraint, not a suggestion: the model reasons over a focused, high-signal set instead of a sprawling pile where the single best source has to compete for attention against a dozen mediocre ones. The cap is the moment the pipeline commits to quality over quantity. ## Why business teams care Context overload is a quiet quality killer. As irrelevant material dilutes the good stuff, answers grow vaguer, hedge more, and take longer to arrive — and none of that shows up as an obvious error, which makes it hard to diagnose. Capping document count keeps responses sharp and predictable, and it places a firm upper bound on the tokens any single answer can consume, which turns a fuzzy cost risk into a fixed, knowable ceiling. ## How to tune it in practice Think in terms of how many sources a thoughtful human would actually need to answer the question. Transactional lookups — a balance, a policy clause, a single fact — usually need one or two. Comparative or synthesis questions may justify more. Raise the cap only when you can see answers genuinely improving with additional sources; if quality plateaus, the extra documents are pure cost and noise. Lower it the moment answers start hedging or wandering. ## Common failure modes it prevents The headline failure is the 'needle in the haystack' problem: the correct source is present but buried so deep in the context that the model underweights it. A tight Max Docs prevents this by ensuring only the most relevant sources make the cut. It also prevents runaway token costs from a single query that happened to match an unusually large number of documents — without a cap, one broad question can quietly become the most expensive request of the day. ## Where it fits in the stack Max Docs works hand in hand with Re-Rank and Snippet Size. Re-Rank decides the order, Max Docs decides how many of the top results survive, and Snippet Size decides how much of each one is sent. Together they form the context-budgeting layer of the pipeline — the trio that determines exactly how much, and how good, the evidence the model finally sees will be. ## Tuned per use case A nuanced research or comparison query may warrant a higher ceiling so the model can weigh multiple viewpoints; a quick factual lookup needs only one or two sources and benefits from the speed. The cap is a tunable trade-off between thoroughness and focus, set once per use case and adjusted as you learn what each workflow actually needs. > Giving a model more context isn't generosity — past a point, it's noise the model has to fight through. ## The takeaway Max Docs enforces context discipline: a hard ceiling that keeps answers focused, fast, and cost-bounded by sending the model only its best sources — never a haystack to search. --- From NeuralSeek's AI Grounded — practical, web-verified guidance on building governed, grounded enterprise AI. NeuralSeek is the model-agnostic, governed AI platform you own: any LLM (swap with no rebuild), your data in your own tenant (cloud or on-prem), 118 guardrails enforced before any action, one container that runs anywhere.