General issues

[mgalore]

Description of the bug:

Function Calling Behavior Issues: Tool Usage Reluctance: Even when tools are properly defined, Gemini often refuses to use them, claiming it "can't access files" or needs permission, despite being explicitly given permission in the API. System Message API Inconsistency: The parameter for setting system messages seems to be inconsistent or not well-documented (system_instruction doesn't work in your version). Response Structure Issues: Response Structure After Tool Calls: The documentation doesn't clearly explain what the response structure looks like after a tool call is executed and how to properly process it. Missing Response Parts: Sometimes the response doesn't contain text parts after function calls, which isn't well-documented or handled gracefully by the API. Debugging Challenges: Error Messages: The error messages for function calling aren't very descriptive or helpful for debugging. Logging/Tracing: There's no built-in way to see what Gemini is thinking when deciding whether to use tools or not. Documentation Gaps: Version Compatibility: The library doesn't make it clear which features are available in which versions. Function Calling Examples: Limited examples showing correct implementation of function calling workflows.

Actual vs expected behavior:

No response

Any other information you'd like to share?

No response

[Gunand3043]

Hey @mgalore , Thanks for the detailed feedback. We would like to know which model is causing the issue regarding tool usage. If you could provide us with sample code to reproduce the issue on our end, that would be really helpful. Thanks..

[github-actions[bot]]

Marking this issue as stale since it has been open for 14 days with no activity. This issue will be closed if no further activity occurs.

[github-actions[bot]]

This issue was closed because it has been inactive for 28 days. Please post a new issue if you need further assistance. Thanks!