MCP server for Olympus health data - gives Claude access to your health metrics
Five tools with clear verb-noun naming (get_*) and reasonable descriptions (100-180 chars). All tools are READ_ONLY and well-scoped. However, input schemas are incomplete: only 2 of 5 tools have documented input parameters with type/description; 3 tools (get_todays_metrics, get_health_summary, and implicitly others) lack visible parameter schemas. Output schemas are not documented anywhere in the source. Parameter descriptions are minimal (e.g., 'Number of days to retrieve (default 7)' lacks range constraints). No error handling guidance visible. Tool descriptions are adequate but generic, they state WHAT but not WHEN to use each tool or how they differ from similar tools.
Get a comprehensive health summary combining today's metrics, sleep, HRV trend, and recent workouts
Get Heart Rate Variability trend data over the past N days with daily averages, min/max, and trend analysis
Get recent workouts from the past N days with summary statistics and detailed workout information
Get sleep data for the past N days with averages and detailed night-by-night breakdown
Get today's cumulative and point-in-time health metrics including steps, calories, HRV, heart rate, and sleep
Two tools (get_todays_metrics, get_health_summary) have no visible input schema definition in source code. Cannot verify parameter types or constraints.
Output schemas are not documented. LLMs cannot predict response structure, field names, or types. Breaks downstream tool chaining and forces parsing guesswork.
Parameter descriptions lack range constraints. 'days' parameter accepts 1 - 365 but no bounds stated. LLMs may pass absurd values (0, 999, negative).
No error handling guidance. If database query fails, user receives raw error. No recovery hints (e.g., 'No data found, try a larger date range').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Tool descriptions do not explain WHEN to use each tool or how they differ. 'get_health_summary' combines sleep, HRV, metrics, and workouts, but descriptions don't clarify when to call it vs. individual tools.