fix(bedrock): handle None value of "parameters" correctly #17256
+97
−47
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.
Title
fix(bedrock): handle None value of "parameters" correctly
Relevant issues
Pre-Submission checklist
Please complete all items before asking a LiteLLM maintainer to review your PR
tests/litellm/directory, Adding at least 1 test is a hard requirement - see detailsmake test-unitType
🐛 Bug Fix
✅ Test
Changes
Some agent frameworks provide a None value when a tool has no parameters. For example,
{"type":"function","function":{"name":"weather","description":"Get current weather information","parameters":null}}The bedrock function
_bedrock_tools_ptis usingdict.get(key, default)which provides a default value only when there is no such key. However, when the key is present and isNone, the default value will not be used. In such case, litellm will raise a KeyError when trying to pop$defsfrom None.This PR changed the way of bedrock checking parameters, by adding a if-check on parameters and setting the default value