-
Notifications
You must be signed in to change notification settings - Fork 197
fix: tolerantly decode stringified JSON object arguments in MCP tool calls #9821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
7268702
fix: tolerantly decode stringified JSON object arguments in MCP tool …
nishantmonu51 4bf9cd5
fix: reject trailing content after decoded JSON in stringified-arg co…
nishantmonu51 55165a4
fix: search only allOf branches when locating property and items sche…
nishantmonu51 e37e1b7
fix: derive effective types from allOf branches by intersection in co…
nishantmonu51 924095d
fix: bound schema-driven recursion in propertySchema and itemsSchema
nishantmonu51 712f9bc
feat: gate MCP tolerant argument decoding behind the `mcp_tolerant_ar…
nishantmonu51 cf03b92
test: add mcp_tolerant_args to expected feature flag maps
nishantmonu51 b52b44f
fix: address review feedback on MCP tolerant argument decoding
nishantmonu51 d11e322
docs: document `rill.ai.mcp_tolerant_args` in the rill.yaml schema
nishantmonu51 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the coercing is a little risky, maybe only do it as a fallback when the normal code actually fails to parse? E.g. could be something like this: