Server has 10 tools with complete input schemas and descriptions. Naming follows verb_noun pattern (getWeeklyVolume, getActivities, etc.). Descriptions are detailed (100-300 chars) and explain WHEN to use each tool. However, several tools expose deprecated parameters (summary flag alongside includeSummaryOnly in getActivities, getHeartRateData, getWeightData, getSleepData, getTrainingStressBalance), creating confusion. Output schemas are not explicitly documented in the source. Error handling returns generic messages without recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite all tools being READ_ONLY. Parameter descriptions are thorough but some lack explicit constraints (e.g., week 1-53 is stated but not enforced in schema).
Retrieve recent activities to analyze training history and patterns. Enables analysis of recent workouts, tracking training volume, identifying activity types, and monitoring performance trends. Essential for understanding training load, recovery needs, and progress toward goals. Supports pagination for efficient data access.
Retrieve comprehensive details for a specific activity to enable deep performance analysis. Provides complete activity data including splits, cadence, elevation, training effects, and advanced running metrics. Essential for analyzing individual workout performance, understanding training stimulus, and identifying areas for improvement.
Retrieve comprehensive daily summary to understand overall health and training status. Provides a unified view of sleep quality, daily activities, and key health metrics in a single request. Essential for daily check-ins, identifying trends, and making training decisions. Gracefully handles partial data availability if individual services are temporarily unavailable.
Retrieve aggregated health metrics to monitor daily wellness and recovery. Provides a flexible way to access multiple health metrics in a single request. Essential for tracking daily health trends, monitoring recovery indicators, and identifying correlations between different health markers. Gracefully handles individual metric failures.
Deprecated parameter pattern: 5 tools expose both 'summary' (deprecated) and 'includeSummaryOnly' (current). LLMs will be confused about which to use, and the dual parameters violate single-responsibility principle.
Missing tool annotations: All 10 tools are READ_ONLY but lack readOnlyHint annotation in schema. This prevents agents from understanding safety guarantees and optimizing retry/caching strategies.
Output schemas not documented: Source code shows tool implementations but does not expose return type schemas to the MCP protocol. LLMs cannot plan downstream operations without knowing response structure.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | <=2025-11-25 | v2 |
Retrieve detailed heart rate data to monitor cardiovascular health and recovery. Provides resting heart rate, daily min/max, and time-series data for tracking cardiovascular fitness and recovery. Resting heart rate is a key indicator of fitness improvements and recovery status. Time-series data enables detailed analysis.
Get daily hydration (water intake) data.
Retrieve comprehensive sleep data to analyze sleep quality and recovery. Enables analysis of sleep patterns, sleep stages (deep/light/REM), and recovery metrics. Essential for understanding rest quality, identifying sleep issues, and correlating sleep with training performance. Supports filtering to reduce response size.
Get training stress balance (TSB), chronic training load (CTL), and acute training load (ATL) for a specific date. Supports summary mode using 'trainingStress' preset which excludes time-series data while preserving current CTL/ATL/TSB values and summary statistics.
Aggregate weekly training volume to track training load patterns. Calculates total training volume for a specific week including duration, distance, elevation, and calories. Essential for monitoring training consistency, identifying volume trends, and planning progressive overload. Supports activity-type breakdown for multi-sport athletes.
Access body composition including weight, BMI, body fat, and muscle mass.
Weak error messages: Error responses return generic strings like 'Failed to get weekly volume: <error>' without recovery guidance. LLMs cannot determine if the error is retryable, user-fixable, or fatal.
Minimal descriptions for simple tools: getWeightData (50 chars) and getHydrationData (45 chars) lack context on WHEN to use them vs related tools. Descriptions should be 50-200 chars and explain use cases.