KC Royals: 3 big club questions, 3 answers
Some important questions face the Royals as they prepare for four games against the majors' best team.
![](https://images2.minutemediacdn.com/image/upload/c_crop,w_6000,h_3375,x_0,y_160/c_fill,w_752,ar_16:9,f_auto,q_auto,g_auto/images/GettyImages/mmsport/7/01h3g0b93j2vct028tae.jpg)
For the time being, the KC Royals are no longer the worst team in the majors. Oakland is after losing six straight times, and even if the A's clinch their 20th win against Cleveland tonight, they'll still be bringing up the rear by percentage points.
The Royals, now 20-54 after blowing another early lead and losing to Detroit 9-4 Wednesday, a defeat brought about primarily by poor outings by starter Brady Singer, who gave up five earned runs in seven innings, and reliever Jackson Kowar, who handed the Tigers four unearned runs on four hits in the in the inning he worked, helped themselves a bit by beating Detroit Tuesday. But coupled with Monday's defeat, Wednesday's saddled the Royals with yet another in their long line of series losses.
And brings to mind three questions heading into the next leg of KC's current 10-game road trip, a four-game series with Tampa Bay that begins Thursday evening.
What should KC Royals fans expect from their four contests with Tampa Bay?
Not much. Remember that while Kansas City started the season horrendously and hasn't really improved, the Rays came out and have remained hot—their 52-25 record is baseball's best and they've occupied first place in the American League East since Opening Day.
None of that, especially the scheduled pitching matchups, bodes well for the Royals, who'll face Tampa's best two starters, Shane McClanahan (11-1, 2.12 ERA) and Zach Eflin (8-3, 3.26), in Games 1 and 2. McClanahan, a lefty, leads the majors in wins and ERA and is 1-0 in two career starts against Kansas City. Eflin has lost his last two decisions, but won eight of his first nine decisions. He shut out the Royals in his only career appearance against them.
The Rays haven't announced their Game 3 starter but will send Tyler Glasnow, 2-1, 4.97, to the mound Sunday.
The Royals will counter Thursday night with opener José Cuas, who's 3-0, 4.15 as a reliever this season but has never started or opened a major or minor league game. Friday night, Zack Greinke (1-7, 4.81) will seek his sixth win since returning to Kansas City, while Jordan Lyles (0-11, 6.89) gets Saturday's game and Daniel Lynch, who pitched superbly to beat Detroit 1-0 Tuesday, takes his 1-3, 4.45 record into Sunday's series finale.
Tampa's bats pose much danger for those four starters: the Rays' 119 homers lead the AL, their 428 runs and 689 hits rank second only to Texas, they've stolen an AL-leading 96 bases, and they walk more than any other club in the league.
All things considered, then, don't expect the Royals to sweep. And they might leave Tripicana Field without a win.
Why did the KC Royals decide to keep struggling pitcher Mike Mayers?
Good question. Remember that the club DFA'd Mayers Sunday after he surrendered six runs to the Angels in five innings the day before. (Despite Mayers' performance, the Royals won that game on Samad Taylor's exciting ninth-inning RBI single). Unsurprisingly, no team claimed Mayers on waivers, and he accepted an outright assignment to Triple-A Tuesday.
Easy to understand is Mayers agreeing to join the Storm Chasers, for whom he was 2-1, 6.88 when Kansas City called the eight-year big league veteran up last month; after all, he needs a place to play. Much harder to understand, though, is why he's still with the organization. His career 5.10 ERA was a red flag when the club signed him in December, he gave up eight runs in 14.1 Cactus League innings this spring, and was battered for 16 earned runs in the last 13 innings he pitched before his Sunday DFA. He's 1-2 with a 6.15 ERA.
So, just how has he survived with the Royals? Probably for one reason and one reason only—this is a club poor on pitching and pitching depth, and will be more so after the trade deadline. He may not be much, but Mayers is part of all they've got for 2023.
And that isn't saying much. Not much at all.
Is there any chance the KC Royals will pursue outfielder Wil Myers?
If there is, there shouldn't be. Simply put, another outfielder, especially one who's 32 and hitting .189 in his 11th major league season and who Cincinnati DFA'd Tuesday, isn't a commodity the Royals need.
Myers just won't add sufficient value to a Kansas City team steeped with talented young outfielders, so claiming Myers on waivers, which no club had done when this story went live on Kings of Kauffman, would be pointless.
Yes, the Royals considered Myers a major league star of the future when they took him in the third round of the 2009 amateur draft, and after he hit .315 with 14 homers in A-ball in 2019 and homered 37 times and batted .314 two years later in a season split between Double-A and Triple-A, he seemed ready to become that star.
But Kansas City, on the verge of contention after so many years of losing, needed pitching badly and used Myers to get it. The Royals included him in the package of players they shipped to Tampa Bay for James Shields and Wade Davis after the 2012 campaign. One of the finest trades in Royals' history, the deal helped the club get to the World Series in 2014 and win it in 2015.
Myers went on to become a star of sorts, but not a superstar. He hit 28 homers for San Diego in 2016 and 30 for them the following year, but has averaged better than .261 only twice—.293 in his 88-game 2013 rookie season, and .288 in 55 games in 2020. His career average is .252.
No, Myers' is not a body of work that justifies taking playing time from hot KC prospects Dairon Blanco, Samad Taylor, MJ Melendez, Drew Waters, Edward Olivares, or Kyle Isbel when he returns from the Injured List. It's time to let them play and see what they can do.
ASG update. Is Salvy still in the All-Star running?. dark. Next