examples: resolve invalid tool usage status code 400 if llm makes a mistake gpt-oss #569
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.
The bug this fixes.
Sometimes the LLM can make a mistake in the tool's name. The client would output
Tool x not found
and submit a new chat request. The problem is that the chat request will contain the assistant tool request, but will be missing a tool response. This results in an HTTP status code 400,invalid tool usage
.The patch adds a tool response when the tool is not found. This will enable the client to inform the LLM that it performed a bad tool call as a tool response and avoid the HTTP 400 error.
Test with a prompt that will invoke many tool calls like
I need the weather conditions for each state capital in the United States.