Trim Token-Heavy Results
Return concise context to save model budget.
Trim Token-Heavy Results is a free MCP Academy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the MCP Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Results Cost Tokens
Whatever your tool returns becomes part of the model's context, and every character spends tokens. Bloated output is real cost. 💸
Big Results Crowd Context
A giant blob can fill the model's limited context window, pushing out earlier messages and leaving less room to actually reason.
Return Only What's Needed
Send back just the fields the task needs. A focused result helps the model far more than dumping an entire raw record.
Drop Noisy Fields
Strip internal ids, timestamps, and metadata the model will never use. Pick only the relevant keys before you return them.
return {"name": row["name"], "price": row["price"]}Paginate Large Lists
For long results, return one page with a cursor instead of thousands of rows. The model can ask for more only if it needs it.
Cap the Output Size
Set a hard limit on result length and truncate beyond it, so one runaway query cannot flood the model with megabytes of text.
text = full[:2000]
if len(full) > 2000:
text += "...[truncated]"Summarize Before Returning
Sometimes a short summary beats raw data, especially for logs or documents where the model only needs the gist, not every line.
Prefer Compact Formats
Pretty-printed, deeply nested JSON wastes tokens. A flat, compact shape carries the same facts with far fewer characters.
Hand Off Big Data as a Resource
For truly large content, return a resource link the model can read on demand instead of inlining the whole payload every call.
Trim Errors Too
Long stack traces eat tokens fast. Return a short, clear error message and keep the full trace in your server-side logs.
Lean Output, Better Answers
Concise results save budget and sharpen reasoning. A focused reply gives the model exactly what it needs and nothing extra.
Quick Check
Why trim a tool's output before returning it?
Recap: Keep It Lean
You returned only needed fields, paginated, capped size, summarized, and offloaded big data, so results stay token-efficient. 🎯
Frequently asked questions
Is the “Trim Token-Heavy Results” lesson free?
Yes — the full text of “Trim Token-Heavy Results” is free to read here on the web, and the MCP Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the MCP Academy course, upgrade to CoddyKit PRO.
What will I learn in “Trim Token-Heavy Results”?
Return concise context to save model budget. You practise MCP Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start MCP Academy?
No prior experience is required. MCP Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Trim Token-Heavy Results” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this MCP Academy lesson?
Yes. Every MCP Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Async Tools That Don't Block
- Concurrency & Backpressure
- Trim Token-Heavy Results
- Scale Horizontally with Sessions