Is capping tool response size inside execute the right pattern?
AgentTools
We hit
If I understand this correctly, I think the reason why they didn't help is because:
-
-
- So the tool result goes straight to the LLM and blows up the context window.
Our workaround: We cap the tool response inside the tool's execute function before returning it. For arrays, we keep whole items that fit within a budget. The budget is derived dynamically from the model's context window.
Is this the right approach? Or is there a built-in Mastra way to handle oversized tool results that I'm missing? Should I be using processInputStep differently to truncate individual message content?
(This is a bit of a priority for us since our agent is live and consistently crashing because of this issue)
context_length_exceeded If I understand this correctly, I think the reason why they didn't help is because:
-
processInput-
processInputStepTokenLimiter- So the tool result goes straight to the LLM and blows up the context window.
Our workaround: We cap the tool response inside the tool's execute function before returning it. For arrays, we keep whole items that fit within a budget. The budget is derived dynamically from the model's context window.
Is this the right approach? Or is there a built-in Mastra way to handle oversized tool results that I'm missing? Should I be using processInputStep differently to truncate individual message content?
(This is a bit of a priority for us since our agent is live and consistently crashing because of this issue)
