Gemini API Compatibility Issue: Box Remote MCP tool names rejected due to length/characters I am trying to use the Box MCP Server Remote with a tool that connects to Google Gemini / Vertex AI API. Authentication seems to be fine however, the connection is failing with a FIELD_INVALID error. Gemini's API requires all MCP tool/function names to be under 64 characters and contain no special characters. It appears one of the tools being provided by the Box Remote MCP server violates this naming convention (specifically the tool at index 28 in the payload). Could the remote server's tool names be updated to comply with the <64 character limit so it can be used with Gemini?Specific Gemini response:Something went wrong. Here's the specific error message we encountered: An error occurred while processing the request: [{ "error": { "code": 400, "message": "The GenerateContentRequest proto is invalid:\n * tools[0].function_declarations[28].name: [FIELD_INVALID] Invalid function name. Must start with a letter or an underscore. Must be a-z, A-Z,