[Update from Google Cloud Platform Support]
Below is the message we received from the GCP Support team. We appreciate the prompt response (pun intended) and commend Google’s team on the work being done to resolve this for us and everybody else affected by this issue.
Excerpt from the response:
After checking the issue internally, it seems this issue is from the backend. We are working on this and will provide an update on or before Monday, September 7, 2026, at 10 PM IST.
We have some answers to your provided queries; please find them below in the sequence you requested:
The agent initializes and lists the tools because the initialization phase is handled by a separate routing mechanism from the actual tool execution. However, the execution of the tools relies on a specific backend [REDACTED]. Because of some recent changes in the backend, it skips the tool invocation step.
When the tool call was silently skipped by the backend, the agent’s reasoning loop lacked any context or results to proceed, causing it to break and terminate early without generating a final output.
No, there are no new, undocumented configuration requirements for remote MCP servers. This behavior is strictly a regression caused by the unintended ablation of the CALL_TOOLS infrastructure flow.
We will update this thread as we hear more from the GCP support team.