Docs · Questions
LOPsError
How do I fix issues with the `Gemini Live` LOP?
Problem
Users have reported several distinct issues with the Gemini Live LOP, ranging from outdated models to tool integration problems.
1. Outdated Models & MCP Server Error
- Symptom: The default models listed in the
GeminiLivedropdown menu are no longer supported by Google, and the associated MCP server fails to load with aPydantic-fastmcpcompatibility error. - Solution: This is a known issue.
- Models: Manually change the
Model IDparameter in theGeminiLiveLOP to a currently supported Google model (e.g.,gemini-1.5-pro-latest). - Server Error: This is a dependency conflict. You can fix it by running the following commands in the LOPs Python Manager:
pip uninstall fastmcp -y pip install fastmcp==2.8.0 pip uninstall mcp -y pip install mcp==1.9.4
- Models: Manually change the
2. Gemini Live Doesn’t Use LOPs Tools
- Symptom:
Gemini Livedoes not seem to recognize or use other LOPs that have been configured as tools. - Solution: This is often a configuration issue. Here is a checklist to debug the problem:
- Ensure the
Use LOP Toolsparameter on theGemini LiveLOP is turned on. - Verify that the tools are correctly defined in the agent’s configuration (e.g., in the
Tool DAT). - Check that the agent’s
System Message(its main prompt) explicitly gives it permission to use tools.
- Ensure the
3. No Real-time Chat Visualization
- Symptom: You cannot see the conversation history from
Gemini Livein anAgent Sessionviewer in real-time. - Solution: This is not a currently supported feature. The
Gemini LiveLOP is designed for real-time audio interaction, and its conversation history is not directly piped to theAgent SessionLOP.- Workaround: For debugging purposes, you can log the output of the
Gemini LiveLOP to aDATto create a manual transcript of the conversation.
- Workaround: For debugging purposes, you can log the output of the