Every result reports its rozmiar. Nothing is cut silently.
Your AI client can set a size budget for a result. Whole rows are kept until it is spent, and whatever did not fit is reported with a link to the complete result.
What your Network Agent does for you
Your AI client always knows how much of its context a result will use, and never gets a result that was quietly cut. The budget is resolved for every call: the size the client asks for, otherwise your organization’s setting, otherwise a default for the client in use. Whole rows are kept until the budget is spent, and the rest is reported with a link to the complete result.
An AI client reads every result it is handed. When a result is too large, most clients truncate it, drop it, or stop and ask you to narrow the question, and nobody tells you which rows were lost. With a token budget:
- Every result says how big it is, in tokens, the unit an AI client’s context is measured in.
- Your AI client can set a budget for a call. Whole rows are kept in order until it is spent. A row is never cut in half, and at least one whole row always comes back.
- What did not fit is reported: how many rows were left out, one sentence on how to get them, and a link that opens the complete result in Query Builder.
- The budget follows a fixed order: the size the client asks for on the call; otherwise your organization’s Result size if an admin set one; otherwise a default for the AI client calling (see Client-aware defaults).
| Sytuacja | Before | With a token budget |
|---|---|---|
| A 2,000-row answer in a chat app | The client reads part of it and you cannot tell which part. | The rows that fit, plus how many more there are and a link. |
| A wide result in a coding tool | The result spills or is dropped, and the client asks again. | The result fits the first time. |
| “How big is this going to be?” | Unknown until it arrives. | The size is in every answer. |
The plan it needs
| Plan | This capability | Uwagi |
|---|---|---|
| Bezpłatny | Not on this plan | Works as it always has, with standard results. |
| Personal Core, Personal Plus | Dołączony | Part of Context management. |
| Business Core, Business Plus, Business Max | Dołączony | Part of Context management. |
| Enterprise Core, Plus, Max | Dołączony | Part of Context management. |
Why it is on paid plans: your Network Agent does the heavy lifting next to your database, so the rows stay in your network and your AI client spends its attention on the thinking. That groundwork is what the paid plans add.
The Free plan works as it always has. Paid plans add the Analytic toolset. Free is a plan you keep: MCP, the REST API, federated queries and alerts, with the same results as before. Plan names and prices are on the strona z cenami.
How to ask
You do not call tools yourself. Ask in plain words and your AI client picks the tool. Three asks that bring this capability in:
Show me last month’s orders, but keep the answer under 8,000 tokens.
How much of your context did that last result use?
Give me what fits and a link to the full result for the rest.
For people who read tool lists: max_tokens NA qs_run_query oraz qs_run_saved_query (at least 2,000; a smaller value is raised to the floor). The result reports approx_tokens, budget_tokens, budget_source oraz budget_rows_dropped in its diagnostics. See it on the Tools tab.
What comes back
List every open order line with its item and quantity. Keep it under 8,000 tokens.
The first rows of 2,000 fit the 8,000 tokens you asked for. The first three:
| order_no | item | qty | due |
|---|---|---|---|
| SO-10418 | ITEM-2201 | 40 | 2026-10-21 |
| SO-10418 | ITEM-2310 | 12 | 2026-10-21 |
| SO-10422 | ITEM-0457 | 300 | 2026-10-24 |
The rest were left out, not lost: Open the complete result in Query Builder. Want me to group them by due week instead, so it all fits?
- approx_tokens
- Roughly how many tokens the result costs in your AI client’s context.
- budget_tokens
- The budget that applied to this call.
- budget_source
- Where the budget came from:
input(the call itself),org(your organization’s Result size), orclient_default(the default for your AI client). - budget_rows_dropped
- Whole rows left out to stay inside the budget. When it is above zero the answer also carries a link to the complete result.
What it does not help with
- It does not make the query cheaper for your database. The query runs the same; only what reaches your AI client is sized.
- It does not summarise the rows it leaves out. To learn about all of them, ask for a profil.
- It does not change what Excel, Google Sheets, the REST API or Data Viewer receive. They always get the full result.
Ograniczenia
- The smallest budget is 2,000 tokens, so a typo can never return an empty result.
- Your plan’s rows-per-query limit applies first, then the budget.
- Tokens are an estimate from the size of the result. Your AI client may count slightly differently.
- Results count against your data allowance the same way as every other client.
Ustawienia
Open the MCP page’s Context tab, card What reaches your AI assistant, group Result size. An admin changes it for the whole organization; changes reach connected AI clients within five minutes.
| Ustawienie | Co to robi | Domyślny |
|---|---|---|
| Result size | Automatyczny sizes each result for the AI client in use. Fixed keeps every result under about the number of tokens you enter. | Automatyczny |
A budget your AI client sets on a call beats the organization setting, and the organization setting beats the per-client default. Each key can differ: when you create or edit a key on the MCP page, its Result shaping section sets Inherit (follow the organization), Wyłączony lub Strict (a request cannot loosen the organization’s settings), plus the key’s own Result size. Ten What your AI client sees preview on the same tab runs a saved query through your saved settings and shows the size the client would get.
When your AI client says no
When the server refuses, your AI client receives a code and one sentence, and usually relays it. Quoted sentences are the server’s own words; the parts in italics stand for the ids a real message names.
| Kod | What the server says | Co robić |
|---|---|---|
MCP_FEATURE_NOT_INCLUDED (Free) | Free answers as it always has. Setting max_tokens on Free is refused with the context management sentence below; a call that sets none runs normally. | Leave the size to the client, or move up to Personal Core. |
MCP_FEATURE_NOT_INCLUDED | “Your plan does not include context management; schema by business area, shaped results and a size budget are available on Personal Core.” | Your AI client carries on without the input and gives you the plain result. To keep the capability, move up to Personal Core. |
MCP_INVALID_INPUT | A negative max_tokens. Negative values are never read as omitted. | Ask for a positive size of at least 2,000 tokens. |
Przykłady
“Keep answers small today, I am on my phone.”
Your AI client sets a small budget on each call, gets the first rows plus the count of what was left out, and offers summaries instead of long lists.
“I need all 2,000 rows in a spreadsheet.”
The client points you to the link in the result. It opens the same query in Query Builder, where you can send the full result to Excel or Google Sheets.
Related
Facts source
Facts on this page: the Query Streams MCP server and Network Agent as of 19 October 2026, with the server’s own refusal sentences quoted word for word. Table and column names in the examples are made up.
Setup trouble?
- Agent shows Offline, or Test connection and Browse are greyed out? Check that the Agent is online → Is the Agent online?

