Skip to main content
Glama
wilkar

Sports Tracker MCP Server

by wilkar

Get Workout Details

get_workout_details

Retrieve detailed workout metrics such as ascent, descent, HR zones, gear, and Suunto extensions using a workout key.

Instructions

Get detailed workout metrics including ascent, descent, HR zones, gear, and Suunto extensions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imperialNo
workout_keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gearNoDevice or gear used (e.g. Suunto watch)
sportYesSport name, e.g. running, cycling, walking
avg_hrNoAverage heart rate in bpm
max_hrNoMaximum heart rate in bpm
peak_epocNoPeak EPOC in ml/kg
start_timeYesISO 8601 formatted start time
step_countNoTotal steps, if applicable
descriptionNoWorkout description or notes
distance_kmYesDistance in kilometers
workout_keyYesUnique workout identifier
ascent_metersNoTotal ascent in meters
calories_kcalNoCalories burned in kcal
descent_metersNoTotal descent in meters
duration_secondsYesActive duration in seconds
heart_rate_zonesNoFormatted time spent in each HR zone
avg_pace_formattedYesPace in MM:SS min/km format
distance_formattedYesDistance with unit, e.g. '5.20 km'
duration_formattedYesDuration in HH:MM:SS format
avg_speed_formattedYesSpeed with unit, e.g. '10.5 km/h'
max_speed_formattedYesMax speed formatted with unit
recovery_time_hoursNoWorkout recovery time in hours
peak_training_effectNoPeak training effect (PTE 1.0 - 5.0)
training_stress_scoreNoTraining stress score (TSS)
cumulative_recovery_hoursNoTotal cumulative recovery time in hours

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether this is a read-only operation, whether it requires authentication, what the output format is, or any side effects. The description only lists metric categories, which is useful but insufficient for a tool with zero annotation coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is concise and front-loads the main purpose. It lists specific metric categories efficiently. However, it could have used the available space to add usage guidance or parameter context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, which helps, but the description lacks essential context: no usage guidance, no parameter semantics, no behavioral notes. For a tool with 2 parameters and no annotations, the description is minimally adequate but leaves an agent guessing about when to use it and what the parameters mean.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for the undocumented parameters. It does not explain what 'workout_key' is, how to obtain it, or what the 'imperial' flag does beyond its default value. The metric list implies some behavior but does not map to the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Get') and resource ('detailed workout metrics') and lists concrete metric categories (ascent, descent, HR zones, gear, Suunto extensions). It is clear what the tool does, though it does not explicitly differentiate it from sibling tools like get_recent_workouts or get_training_summary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The sibling list includes several workout-related tools (get_recent_workouts, get_training_summary, get_recent_activities_summary), but the description does not state what makes this tool the right choice for detailed metrics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.