feat: improve noToolsUsed error message with Tool Protocol guidance #10247
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related GitHub Issue
Relates to: #10246
Roo Code Task Context (Optional)
This PR was created with the assistance of Roo Code to address user feedback.
Description
This PR attempts to address Issue #10246 by improving the error message shown when the model fails to use tools in its response.
The issue reports that users of third-party API providers (OpenAI Compatible) frequently encounter the error message "The model provided text/reasoning but did not call any required tools." This is often caused by the API provider not fully supporting native tool calling.
Changes:
noToolsUsedDetailsmessage in English (en/chat.json) to include guidance about changing the Tool Protocol to "XML" in Advanced Settings when using third-party API providerszh-CN/chat.json) with the same guidanceRationale:
Test Procedure
Pre-Submission Checklist
Screenshots / Videos
N/A - text-only change to error message
Documentation Updates
Additional Notes
This is an attempt to help users who encounter tool calling issues with third-party API providers. The existing Tool Protocol setting already provides the solution, but users may not know to look for it. This change surfaces that guidance directly in the error message.
Feedback and guidance are welcome!
Get in Touch
Available via GitHub for any questions.