Leaderboard Persistence Operations

This tool provides a native persistence layer for leaderboards backed by work boards, supporting operations log_score, fetch_leaderboard, and reset_board. It accepts parameters: operation (required string enum), board_name (optional string with default Leaderboard_DB), player_id (string required when operation=log_score), score (number required when operation=log_score), and metadata (optional JSON string payload describing extra fields). Implementations must parse card description fields as JSON, handle creation of missing boards or score columns safely, and avoid infinite loops. The worker must transform the inputs and any execution results into a response that strictly validates against the system-provided structured output schema, with no extra fields and correct types.