Strong schema definitions and descriptions across 18 tools. All tools have clear verb-noun naming (get_, create_, update_, delete_, search_, list_) and detailed descriptions (avg 150+ chars). Input schemas are well-structured with type constraints, enums, and parameter descriptions. Complex exercise/workout schemas show sophisticated design. Error handling is present with categorized error codes. Main gaps: some parameter descriptions could be more prescriptive about constraints; output schemas not explicitly documented; no confirmation pattern for destructive operations (delete_custom_workout lacks dry-run).
Create a new custom workout with specified exercises and programming
Delete a custom workout by name with confirmation
Estimate the duration of a workout based on exercises and programming
Get detailed information about a custom workout including exercises, sets, and programming
Get Tonal's weekly goal metrics (Volume, Work, Movement Quality Score, Strength Sets, Power Reps, Endurance Sets, Functional Strength Score) with the current week's actual, target, and range plus a recent trend. Optionally filter by metric name. Functional Strength Score is not Tonal's headline Strength Score; use get_strength_scores for the latter.
Get available Tonal movements, optionally filtered by muscle groups
delete_custom_workout lacks confirmation/dry-run pattern. Destructive operations should support preview-then-confirm to prevent accidental deletion.
Output schemas not explicitly documented in tool definitions. LLMs cannot plan downstream calls without knowing what fields are returned (e.g., what does get_workout_activity_details return?).
Parameter descriptions for numeric constraints (e.g., 'days' in get_strength_scores) lack explicit min/max guidance in text. While JSON Schema has minimum:1, LLMs rely on description text to understand bounds.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 68 | 2026-07-28+ | v2 |
Get current muscle readiness percentages for recovery planning
Get recent progress analysis including workout frequency and trends
Get recent workout history with wall-clock and time-under-tension stats plus workoutActivityId values for activity detail or summary lookup
Get Tonal's headline current Strength Score by body region and a compact per-activity trend. This is distinct from the weekly Functional Strength Score goal metric.
Get comprehensive user fitness statistics and current streak
Get one completed activity with performed sets in original order, catalog-resolved movement names, per-set weights, reps, one-rep max, volume, and range of motion. Activity summary IDs from get_recent_workouts are the same workout activity IDs accepted here. Reports totalDuration as wall-clock time and activeDuration as time under tension.
Get a custom workout in editable format with full exercise and set details
Get Tonal's formatted workout summary and per-movement breakdown. Activity summary IDs from get_recent_workouts are the same workout activity IDs accepted here. Reports duration as wall-clock session time and timeUnderTension as active lifting time.
List up to 100 custom workouts created on Tonal and report when additional workouts may exist
List one Tonal workout-activity API page. Offset 0 selects the account's oldest activities and increasing offset advances toward newer ones; rows are displayed newest-first only within the selected page. Use get_recent_workouts for recent sessions.
Search and filter available Tonal movements by muscle groups, equipment, body region, and other attributes
Update an existing custom workout with new exercises and programming
Complex exercise schema (create_workout, update_workout, estimate_workout_duration) has conditional logic (anyOf sets/setDetails) that is not explained in parameter descriptions. LLMs may struggle to construct valid payloads.
Error handling in error-handler.ts categorizes errors well but does not provide recovery guidance for all cases. E.g., 'Unknown tool' error should suggest available tools.