[BUG] Handle escaped JSON in tool call arguments #56
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.
Problem
LLMs occasionally return tool call arguments as escaped JSON strings (e.g.,
'"{\\"month\\": \\"August\\"}"') instead of plain JSON. This caused validation errors when creating AIMessage objects, as the arguments remained strings after a single json.loads() instead of being parsed into dictionaries.Issue link: #52
Solution
Added double-parsing logic in OCIUtils.convert_oci_tool_call_to_langchain() to detect and handle escaped JSON.
Added escaped JSON test case in unit test.
Testing
Validated with real LLM responses showing the escaped JSON pattern:
Output: