UPDATE: Kansas City Chiefs Have Agreed to Terms with Nick Foles Per Report

Forget everything I just said below. The Chiefs have apparently agreed to terms with Foles.

Apparently this happened while I was typing the below post. It is unclear right now what the terms are or who will be released from the roster to make room for Foles. However, at least one player will have to be dropped to make this transaction happen. Also, the Chiefs had the lowest amount of salary cap space in the NFL as of this morning, so I can’t wait to see the details of the contract and how general manager John Dorsey was able to make this happen.

https://twitter.com/RapSheet/status/761049688967483393″ xlink=”href

https://twitter.com/MikeGarafolo/status/761049571476647936″ xlink=”href

More details to come once this story unfolds.

Previous Post:

According to world renown ESPN reporter and NFL insider Adam Scheffer, the Kansas City Chiefs could potentially be in on the Nick Foles Sweepstakes–if you can call it that–and potentially be trying to sing the former Philadelphia Eagle, former St. Louis Ram, quarterback to a deal. Don’t believe me? Here’s the tweet.

https://twitter.com/AdamSchefter/status/761006015630278656″ xlink=”href

While all that was cited were “sources” Scheffer doesn’t usually miss on these reports. I’m not sure what to make of this report at this point. The Chiefs were in a good position over the last three years when it came to a backup QB behind starter Alex Smith. With Chase Daniel in the room, there was a certainty that if Smith went down due to injury, Daniel could run head coach Andy Reid’s offense suitably well. Now that Daniel has departed for “greener pastures”–and I mean that literally because the Eagles are green–there might be some butthole clenching in the offensive meeting room when it comes to the QB2 position. Foles could fix this, I suppose.

Foles is mainly known for his 2013 season with the Eagles when he stepped in during week five for an injured Mike Vick and started slinging touchdowns while, miraculously, avoided getting picked off. In fact, Foles threw 27 touchdowns to only two interceptions over the 10 games he started in 2013. That was quite the feat, and Foles did this while throwing for nearly 3,000 yards during that span as well. And let’s not forget that Andy Reid drafted Foles in 2012, which is probably why this is newsworthy in the first place.

At the end, could Foles be a serviceable backup to Smith? I don’t see why not. But I don’t think he’d be worth the price tag he brought with him or the potential for a media-induced potential quarterback controversy his presence could create. I’m a firm believer that the Chiefs’ QB2 and potential QB of the future is already on the roster and is named Tyler Bray or Aaron Murray. I guess time will tell.

What do you think, Chiefs fans? Should the team pursue Nick Foles? Is this report just dumb and not even worth the time it took me to type this post? Let us know, in the comments below.