# \[Resolved\] Interval/lap infos and metrics for MCP **URL:** \ **Category:** Bug Reports\ **Created:** [June 16, 2026, 7:26pm UTC](https://tempo.discourse.group/t/resolved-interval-lap-infos-and-metrics-for-mcp/43 "2026-06-16T19:26:32Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bjoern.wolf](https://sea1.discourse-cdn.com/flex039/user_avatar/tempo.discourse.group/bjoern.wolf/32/58_2.png) [@bjoern.wolf](https://tempo.discourse.group/u/bjoern.wolf)\ **Post date:** [June 16, 2026, 7:26pm UTC](https://tempo.discourse.group/t/resolved-interval-lap-infos-and-metrics-for-mcp/43/1 "2026-06-16T19:26:32Z")
Another idea. Today I had a lengthy discussion whether my intervals were good or not. Because the session was longer than planed due to bad route choices the overall stats were a bit misaligned. So I told him to look at the actual interval infos. I previously had a look at the app and also saw the laps so I was quite sure he could get this info as well … turns out … no 🤓 I think some quick glimpse into the metrics of the intervals could help a lot to interpret the quality of the session overall. Because the general metrics are not telling the whole story if something is not as expected. And because I am always riding outdoors, it’s quite common that we have to look a bit more into the other metrics rather than just relying on TSS and IF That’s all 🙏🏼 ---
**Author:** ![Marc](https://sea1.discourse-cdn.com/flex039/user_avatar/tempo.discourse.group/marc/32/56_2.png) [@Marc](https://tempo.discourse.group/u/Marc)\ **Post date:** [June 17, 2026, 12:21am UTC](https://tempo.discourse.group/t/resolved-interval-lap-infos-and-metrics-for-mcp/43/2 "2026-06-17T00:21:12Z")
Hey @bjoern.wolf , of course! The `get_workout_details` tool should be returning laps/intervals and their metrics. Would you mind sharing the workout id, so I can investigate? ---
**Author:** ![bjoern.wolf](https://sea1.discourse-cdn.com/flex039/user_avatar/tempo.discourse.group/bjoern.wolf/32/58_2.png) [@bjoern.wolf](https://tempo.discourse.group/u/bjoern.wolf)\ **Post date:** [June 17, 2026, 1:09am UTC](https://tempo.discourse.group/t/resolved-interval-lap-infos-and-metrics-for-mcp/43/3 "2026-06-17T01:09:01Z")
Ok, then we should move this discussion to the bug categorie 🤓 I was also thinking that this should be available and insisted to look further into the details or parameters. Claude then also corrected his statement about Tempo not being able to return laps. Because of the count field for the list and the description for the `get_workout_details`. The workout ID is `153072.` What’s interesting is that the app is showing the laps/intervals in full detail and with all the metrics I need (and yes, I have to admit the average was not _in_ the zone) ---
**Author:** ![Marc](https://sea1.discourse-cdn.com/flex039/user_avatar/tempo.discourse.group/marc/32/56_2.png) [@Marc](https://tempo.discourse.group/u/Marc)\ **Post date:** [June 17, 2026, 1:50am UTC](https://tempo.discourse.group/t/resolved-interval-lap-infos-and-metrics-for-mcp/43/4 "2026-06-17T01:50:22Z")
Thanks for the workout id. I spoke too soon, and upon further investigation, I discovered a feature parity gap between Web and MCP. I’m working on closing the gap, so both FIT laps from bike computers (missing now) and Strava laps and their details are exposed via `get_workout_details`. ---
**Author:** ![Marc](https://sea1.discourse-cdn.com/flex039/user_avatar/tempo.discourse.group/marc/32/56_2.png) [@Marc](https://tempo.discourse.group/u/Marc)\ **Post date:** [June 17, 2026, 7:05am UTC](https://tempo.discourse.group/t/resolved-interval-lap-infos-and-metrics-for-mcp/43/5 "2026-06-17T07:05:09Z")
Hey @bjoern.wolf , this has been fixed and I took the opportunity to include more data points per lap: VAM, min HR, max cadence, avg temp, and CORE sensor temp (min/avg/max).