fix(tools): accept null for optional tool parameters - #15
Merged
Merged
Conversation
- Providers like OpenRouter/Anthropic send null instead of omitting keys for optional tool parameters - The structured output handler converts optionalKey to required T|null in the JSON schema, but the Toolkit decodes with the raw schema that rejects null - Wrap all optional fields with Schema.NullOr across all three tools - Update shouldReset to use == null (catches both null and undefined)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
nullinstead of omitting keys for optional tool parametersoptionalKeyto requiredT | nullin the JSON schema, but the Toolkit decodes with the raw schema that rejectsnullSchema.NullOracross WebSearch, CrawlPages, and SequentialThinkingshouldResetto use== nullto handle bothnullandundefined