The same uploaded Cloud Code script succeeds in Portal Run and Debug, but fails when called through MCP using the same app and parameters.

Inside Cloud Code, the script calls:

leaderboardProxy.getGlobalLeaderboardPageByVersion(
leaderboardId, "HIGH_TO_LOW", 0, 0, 1
);

The original script successfully reads score, rank, and data when executed from the Portal. However, diagnostics during MCP execution show:

• score, rank, and data are undefined.
• The entry contains bestScore, otherData, and tRank instead.
• isClientBridge() returns true; isServerBridge() returns false.

This difference is observable inside the Cloud Code script, before its result is returned to MCP.

Steps to reproduce

1. Use a client-callable Cloud Code script that reads an existing historical division leaderboard.
2. Inspect the first entry’s keys and its score, rank, and data fields.
3. Compare Portal Run and Debug with MCP initClientSession → runScript, using identical inputs.

Expected: consistent entry fields across both execution paths.

Supporting both field formats in our script works around the issue. Is this difference intentional, or could it be a response-conversion bug?