Royals Report: 5 Things About Mets Revenge Sweep

The Royals lost their second straight game to the New York Mets, falling 4-3 Tuesday afternoon at Citi Field. The Mets finished off the mini-sweep by winning two, one-run games over the Kansas City Royals.

The KC Royals fell to 38-33, and three games behind first place Cleveland Indians in the AL Central. The Mets pulled within 3.5 games of the Washington Nationals in the AL East by improving to 38-32.

Not only did the Kansas City Royals lose to the New York Mets twice in the last two games, they also failed to win two late-inning bullpen contests in a row. I’m certain Mets fans view it as a small measure of revenge for last October’s #RoyalsDevilMagic wins, but still wish their team had been able to win the games the really counted.

The KC Royals are now a horrific 13-25 on the road. They came into the series winning three straight games, much like they came into their last road trip riding a six game winning streak. Both times, leaving Kauffman Stadium triggered a losing streak. I can’t think of any clearer evidence that Kansas City’s road troubles have gotten into their heads.

It’s a mental thing that the Kansas City Royals must overcome. If they don’t, they’re likely to fall out of the AL Central race.

On to my observations about Tuesday’s game:

Next: Danny Duffy

4) Royals Really Missed Kendrys Morales vs. Mets

Kendrys Morales has broken out of his two month long slump to hit .317/.388/.483 in June, which pretty much looks like his 2015 performance for the Kansas City Royals. Getting Morales going has been big for the KC Royals offense, which really relies on his switch-hitting power in the middle of their lineup.

More from Kings of Kauffman

• KC Royals Rumors: Is a monster move in the cards?
• KC Royals Free Agent Hunt: 3 Tampa Bay pitchers
• Grading the 2022 KC Royals: The $25 million man
• KC Royals Winter Meetings Tracker: Expectations met
• KC Royals Winter Meetings Tracker: Day 3 update

Of course, playing two games under National League rules meant that designated hitter Morales got parked on the bench. The “hot” Kansas City Royals offense then proceeded to score four runs in two games while Morales made only one plate appearance. They also lost two, one-run games.

Yeah, the Royals missed him.

Let’s just hope that Kendrys Morales picks up where he left after his four day break (off days before and after the Mets series, plus two games under NL rules). Breaking Kendrys momentum was the last thing the KC Royals needed after he wallowed for two months.

I guess the Mets dished out a measure of their own medicine to the Kansas City Royals. I can’t say I enjoyed it much, and I hope that Kendrys Morales can turn things around during the coming homestand.

Next: Joakim Soria

3) Joakim Soria Failed Again

Let’s face it, Kansas City Royals fans, Joakim Soria has been something of a disappointment in the bullpen after signing a three-year, $27 million deal to return to KC. He lost his set-up man role to Kelvin Herrera with a horrible April, regained a role in the Kansas City three-headed monster with a strong May, and now sports a quite respectable 3.09 ERA.

But the KC Royals didn’t bring him back to be “respectable”. The front office was looking to land a top free-agent bullpen arm to continue their recent back end dominance. While the Kansas City Royals still lead major-league baseball in bullpen ERA, they have not been quite the sure thing in the late innings that they have been in the past. A big reason for the slide has been Soria.

Joakim Soria famously failed to nail down a ninth-inning save opportunity to open the Cleveland Indians series on June 2, triggering an eight-game losing streak on the heels of a six game winning string.  On Tuesday, Soria had the chance to help his team prevent the two-game sweep to the Mets. Instead, he gave up a solo home run in the sixth inning right after his team had tied up the game in the top half of the frame.

Matt Reynolds‘ first career home run ended up being the difference in New York’s 4-3 win.

Yes, Ned Yost asked Soria to get one batter in the fifth, sit, then pitch in the sixth. Yes, most teams would still consider Joakim Soria a bullpen asset rather than detriment. But, Soria isn’t the same shut-down guy that saved 160 games in his first stint with the KC Royals.

Next: Alcides Escobar

2) Alcides Escobar Batting Second Is Driving Me Nuts

Not so long ago, I wrote in support of Ned Yost’s decision to bat Alcides Escobar at lead-off, based on psychology. However, once the losing streak caused Yost to shake up his lineup, I would have though it was the perfect opportunity to move Escobar to the bottom of the lineup where his numbers suggest he belongs.

More from KC Royals News

• KC Royals Rumors: Is a monster move in the cards?
• KC Royals Free Agent Hunt: 3 Tampa Bay pitchers
• Grading the 2022 KC Royals: The $25 million man
• KC Royals Winter Meetings Tracker: Expectations met
• KC Royals Winter Meetings Tracker: Day 3 update

Instead, Yost installed him in the no. 2 hole.

Of course, the KC Royals then scored five runs after a string of games in which they only plated four runs in six games. The next night, the Royals broke their eight game losing streak and went on to win eight of their next nine games. Which, of course, locked in Escobar as the team’s no. 2 hitter.

I supposed Yost’s logic might be changing Escobar’s approach at the plate similar to putting Mike Moustakas at no. 2 last season. If hitting behind the fast Whit Merrifield forces Escobar to take more pitches, he might develop more patience. I guess there’s an argument for the move, but I really doubt it will work. I think getting Escobar to take more pitches will just put him down in the count more often, which means he’ll be hacking at more two-strike pitches.

Yes, Escobar stroked two-hits on Tuesday. His slash line improved to a whole .249/.274/.298. He doesn’t take walks. He’s a poor two-strike hitter. And I don’t see any evidence of a changed approach at the plate which would go along with putting him at the no. 2 spot.

To me, putting Escobar at no. 2 looks like he accomplishing nothing but giving more at bats to one of the worst hitters in baseball.

Next: Cheslor Cuthbert

1) Cheslor Cuthbert Hitting With More Authority

The one bright spot from Tuesday’s loss was Cheslor Cuthbert’s solo home run that briefly tied up the game at 3-3. That Joakim Soria allowed the Mets to retake the lead in the bottom half of the inning doesn’t take away from Cuthbert’s clutch hit off of a tough starter in Noah Syndergaard (8-2, 2.08 ERA).

Cuthbert has been pretty darn good in June, slashing an outstanding .288/.347/.832. He’s slammed four home runs and has drawn 6 walks in 66 at bats (73 plate appearances).

After his two-home run game earlier in the month, pitchers have been approaching him with a little more caution, which has helped boost Cuthbert’s walks and on base percentage. Overall, Cuthbert has five home runs in 148 at bats, which suggests he would have high teens to low 20’s home run power over a full season.

The 23-year-old rookie has possessed a quick bat that has suggested he could hit for decent power as a prospect, but he never hit more than 12 home runs in a season during his seven year minor-league career. However, Cuthbert has surpassed double-digit home run totals in both 2014 and 2015.

Next: Royals Road Woes Continue

For the 2016 season, Cheslor Cutbert is slashing a respectable .269/.307/.400 for a 90 wRC+ (10% below a league average hitter. Adjusted Runs Created is a catch-all stat created to measure a player’s overall offense contribution to his team). Let’s hope the real Cheslor Cuthbert is more like June rather than May, and his slash line continues to improve.