[BUG] GEMINI with Tool Calls

[szhengac]

Required prerequisites

• I have read the documentation https://camel-ai.github.io/camel/camel.html.
• I have searched the Issue Tracker and Discussions that this hasn't already been reported. (+1 or comment there if it has.)
• Consider asking first in a Discussion.

What version of camel are you using?

0.2.85

System information

Eigent UV

Problem description

When using Eigent AI agent with Gemini. I received GenerateContentRequest.contents[0].parts[0].function_response.name: Name cannot be empty.

I did some investigation by my own, and I found tool call message is missing when enable_snapshot_clean is enabled and func name is missing. I did some tweak and it seems to be working.

Reproducible example code

Use https://github.com/eigent-ai/eigent with Gemini configuration. And ask it to find the best coffee machine for me.

Traceback

Expected behavior

No response

Additional context

No response

[lightaime]

Hey @szhengac. Thanks for reporting the issue. Which Gemini model did you use? Would you like to open a PR for this fix? Thanks! c.c. @Wendong-Fan

[Chase-Xuu]

I've analyzed and fixed this issue. PR incoming!

Root Cause:
When enable_snapshot_clean is enabled, the _clean_snapshot_in_memory method was only recreating the FUNCTION message (tool result) but was removing BOTH the ASSISTANT message (tool call request) and FUNCTION message from memory.

For Gemini API, both messages must exist together - the tool call request must be present alongside the tool call result. Without the ASSISTANT message, Gemini cannot properly associate the function response with its request, causing the error:
GenerateContentRequest.contents[0].parts[0].function_response.name: Name cannot be empty

Fix:

1. Added args and extra_content fields to _ToolOutputHistoryEntry to preserve tool call context for later reconstruction
2. Modified _clean_snapshot_in_memory to recreate BOTH:
   • The ASSISTANT message (with tool_calls array containing func_name and args)
   • The FUNCTION message (with cleaned result)

This is essentially the same approach as @szhengac's investigation, properly integrated and refined.

Testing:
I verified the syntax is correct. This fix ensures paired tool call request/response messages are properly reconstructed during snapshot cleaning.