Fix: Correctly remove 'additionalProperties' from function schemas for Gemini API #59
+20
−3
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.
Description
This pull request addresses an issue where the
AutoAgent
fails when using the Google Gemini API due to its strict handling of function declaration schemas. The Gemini API does not recognize theadditionalProperties
field, and the existing logic to remove this field was not functioning as intended.This issue appears to be the same as or very similar to the one described in #51.
This patch updates the schema cleaning utility in
utility.py
to correctly and recursively remove theadditionalProperties
field from all levels of the tool function schemas before they are sent to the Gemini API.Type of Change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
additionalProperties
in its function definition now works correctly without raising an API error.Test Configuration: