These 3 Mets roster gambles failed to hit the jackpot this year

Cleveland Guardians v New York Mets
Cleveland Guardians v New York Mets | Elsa/GettyImages
1 of 3

This year’s New York Mets roster might be known for its price tag and the obvious transactions made to try to make them better. Retaining Edwin Diaz and Brandon Nimmo were no-brainers. Signing Justin Verlander to replace Jacob deGrom was the only natural action to take.

The Mets have, like everyone else, taken a few gambles with the roster. They gave players who may not have deserved an opportunity their chance.

Not too many of those riskier maneuvers have paid off. In fact, three Mets roster decisions stand out as gambles that came out red when the team was betting on black.

1) NY Mets roster gamble: Signing Gary Sanchez who never really seemed to have a future in Flushing

Wouldn’t it be nice to have Gary Sanchez on the Mets roster? With the benefit of hindsight, it would certainly be delightful. The team could carry him, Francisco Alvarez, and Omar Narvaez all at once. One could always DH. Another could catch. In the absence of Pete Alonso, we could even throw someone over at first base for a game. This is why the Mets need a crystal ball in their analytics department.

There was never any winning with the minor league signing of Sanchez. Alvarez had already earned his spot on the MLB roster. Narvaez was on his way back shortly before Sanchez’s opt-out was coming. The Mets decided to DFA Sanchez and allow Tomas Nido to find his way back onto the roster. Amazingly, both would get designated for assignment shortly after which practically erased the purpose of signing Sanchez in the first place.

This was a no-win type of move for the Mets who would have only benefitted from having Sanchez if he played well in a short period of time. Sanchez playing well would have required Alvarez to underperform. He would have eventually become trade bait regardless.

A gamble equivalent to asking the blackjack dealer to “hit you” when you’re already at 21, we can blame nothing more than poor timing for how this one worked itself out.

Schedule