Use this workflow for questions such as "How consistently did I train over the last month?"
1. Establish the scope
Identify the connected member or authorized focused client. Resolve the requested period and timezone. For the external connector, start with get_my_connector_profile when those details are not already available.
2. Select the available read
Inspect live tool discovery. The external connector exposes get_my_training_summary when the training domain is enabled and consented. get_my_overview can help establish available domains and coverage.
Follow the live schema's period bounds. Do not call an absent per-session or exercise-history tool just because a related capability exists in the application.
3. Interpret the returned records
Separate planned training from completed sessions. State the period, session count, sets, repetitions, and other returned metrics with their units and definitions.
Use the returned coverage and warnings. Missing sessions or unsynced data are not proof that the athlete skipped training.
4. Compare carefully
When supported, request the explicit previous-period comparison. Report both periods and their own coverage. Do not compare an incomplete week with a full week without explaining the difference.
Exercise variations, equipment, and unit changes can affect comparisons. Avoid introducing a new personal-record or volume calculation when the tool already defines one.
5. Give the result
Summarize the observed pattern, cite the returned values, and distinguish a factual observation from a suggestion. A read request does not authorize changing the member's plan.
For unavailable data, say what the current connection can and cannot return. Do not replace missing data with another member's information.
See workouts and sessions and data conventions.