@trainheroic-unofficial/athlete-mcp 0.6.2 → 0.6.3

package/dist/server.mjs

@@ -837,6 +837,28 @@ function selectWorkouts(list, opts = {}) {
 	if (opts.limit !== void 0) out = [...out].sort((a, b) => a.date < b.date ? 1 : a.date > b.date ? -1 : 0).slice(0, opts.limit);
 	return out;
 }
+/**
+* Project presented workouts to compact headers (date/title/program + logged flag + exercise
+* counts), dropping the per-set block detail. A dense multi-program week of full views can be
+* tens of KB; this keeps an overview question to one small row per session, with a drill-in
+* (narrow the date range) when the detail is actually needed.
+*/
+function summarizeAthleteWorkouts(list) {
+	return list.map((w) => {
+		const exerciseCount = w.blocks.reduce((n, b) => n + b.exercises.length, 0);
+		const performedCount = w.blocks.reduce((n, b) => n + b.exercises.filter((e) => e.performed.length > 0).length, 0);
+		return {
+			id: w.id,
+			date: w.date,
+			title: w.title,
+			program: w.program,
+			team: w.team,
+			logged: w.logged,
+			exerciseCount,
+			performedCount
+		};
+	});
+}
 const MAX_PARAM_SLOTS = 10;
 /**
 * Build the body for `PUT /1.0/athlete/savedworkoutsetexercise/{id}`. The body uses
@@ -1103,9 +1125,21 @@ function registerProfileTools(server, ctx, whoami, userId) {
 		return jsonResult(await fetchLeaderboard(ctx.client, toId(workoutId), opts));
 	}));
 }
-const ATHLETE_WORKOUTS_DESC = "Workouts in an inclusive YYYY-MM-DD window, flattened to blocks/exercises. Each exercise carries both its `prescribed` sets (what the program called for) and `performed` sets (what the athlete actually logged); each workout has a top-level `logged` flag. Use `performed`/`logged` to tell what was recorded or done. That is the reliable signal: a session can hold logged sets while the API's own completion flags stay 0, and an empty `performed` means nothing was logged for that exercise. For 'did I record anything / what did I do', set loggedOnly:true to return only sessions with logged sets (it keeps whole sessions that have any logged set, so individual exercises inside can still show empty `performed`; it also shrinks a large result); limit returns the most recent N workouts (newest first). For 'what's my next workout', query a forward window from today; if it comes back empty, the most recent session is likely yesterday's still-unlogged one, so widen the window backward a day or two. Both filters apply to the presented view, not raw. raw:true returns the untouched API objects. This is a date-windowed fetch, NOT an aggregate: for lifetime totals (all-time session count, total volume, first/last logged date) call athlete_profile instead of summing windows — a multi-year range here can time out. Narrow the window if the result is truncated.";
-const ATHLETE_EXERCISE_HISTORY_DESC = "Per-exercise PRs and the dated session time-series (sets performed, estimated 1RM). The returned `sessions` run all-time, newest first; pass since/until (YYYY-MM-DD, inclusive) to keep only sessions in that window — use it for 'last 3 months' / 'this year' questions so the result stays small. `liftPRs` are always all-time and ignore since/until. Set raw:true for the untouched API object. Get the exercise id from athlete_exercises.";
-const ATHLETE_EXERCISES_DESC = "The exercises the athlete has logged (id + title + positional units). Pass q to free-text search by name; use the returned id with athlete_exercise_history, athlete_personal_records, or athlete_exercise_stats (all of which require an exercise id).";
+const ATHLETE_WORKOUTS_DESC = "Workouts in an inclusive YYYY-MM-DD window, flattened to blocks/exercises. Each exercise carries both its `prescribed` sets (what the program called for) and `performed` sets (what the athlete actually logged); each workout has a top-level `logged` flag. Use `performed`/`logged` to tell what was recorded or done. That is the reliable signal: a session can hold logged sets while the API's own completion flags stay 0, and an empty `performed` means nothing was logged for that exercise. For 'did I record anything / what did I do', set loggedOnly:true to return only sessions with logged sets (it keeps whole sessions that have any logged set, so individual exercises inside can still show empty `performed`; it also shrinks a large result); limit returns the most recent N workouts (newest first). For a high-level overview ('what's on my schedule this week', 'what have I been training lately') set summary:true to get one compact row per session (date, program, title, logged flag, and exerciseCount/performedCount — read performedCount against exerciseCount, e.g. 1 of 12 logged) instead of every set — a multi-program week of full detail is large, so prefer summary first, then re-query a single day without it to drill into that day's sets. For 'what's my next workout', query a forward window from today; if it comes back empty, the most recent session is likely yesterday's still-unlogged one, so widen the window backward a day or two. Both filters apply to the presented view, not raw. raw:true returns the untouched API objects. This is a date-windowed fetch, NOT an aggregate: for lifetime totals (all-time session count, total volume, first/last logged date) call athlete_profile instead of summing windows — a multi-year range here can time out. Narrow the window if the result is truncated.";
+const ATHLETE_EXERCISE_HISTORY_DESC = "Per-exercise PRs and the dated session time-series (sets performed, estimated 1RM). The returned `sessions` run all-time, newest first; pass since/until (YYYY-MM-DD, inclusive) to keep only sessions in that window — use it for 'last 3 months' / 'this year' questions so the result stays small. estimated1RM is a formula off the session's best set and reads high when a session mixes a heavy single with high-rep backdown work, so treat it as approximate, not a logged single. `liftPRs` are always all-time and ignore since/until, but each carries the date it was set, so filter those dates yourself to answer 'PRs set this year'. Set raw:true for the untouched API object. Get the exercise id from athlete_exercises.";
+const ATHLETE_EXERCISES_DESC = "The exercises the athlete has logged (id + title + positional units). Pass q to free-text search by name; use the returned id with athlete_exercise_history, athlete_personal_records, or athlete_exercise_stats (all of which require an exercise id). A common name returns several variants (e.g. plain 'Bench Press' id 1162 vs 'BARBELL BENCH PRESS'); each variant keeps its own separate history and PR board, so prefer the plain canonical entry, and if a PR or trend looks incomplete, the work may be split across variants — check the others.";
+function runAthleteWorkouts(ctx, args) {
+	return attempt(async () => {
+		const workouts = await fetchAthleteWorkouts(ctx.client, args.startDate, args.endDate);
+		if (args.raw === true) return jsonResult(workouts, { hint: "Narrow startDate/endDate to shrink this result." });
+		const opts = {};
+		if (args.loggedOnly !== void 0) opts.loggedOnly = args.loggedOnly;
+		if (args.limit !== void 0) opts.limit = args.limit;
+		const selected = selectWorkouts(presentAthleteWorkouts(workouts), opts);
+		if (args.summary === true) return jsonResult(summarizeAthleteWorkouts(selected), { hint: "Compact per-session overview. Re-query a narrow startDate/endDate without summary for a day's full prescribed/performed sets." });
+		return jsonResult(selected, { hint: "Large? Set summary:true for one row per session, loggedOnly:true, pass limit, or narrow the dates." });
+	});
+}
 /** Workouts, exercise catalog, per-exercise history/PRs/stats. */
 function registerExerciseTools(server, ctx, userId) {
 	server.registerTool("athlete_workouts", {
@@ -1116,17 +1150,11 @@ function registerExerciseTools(server, ctx, userId) {
 			endDate: dateString,
 			raw: z.boolean().optional(),
 			loggedOnly: z.boolean().optional(),
-			limit: z.number().int().positive().max(200).optional()
+			limit: z.number().int().positive().max(200).optional(),
+			summary: z.boolean().optional()
 		},
 		annotations: READ
-	}, ({ startDate, endDate, raw, loggedOnly, limit }) => attempt(async () => {
-		const workouts = await fetchAthleteWorkouts(ctx.client, startDate, endDate);
-		if (raw === true) return jsonResult(workouts, { hint: "Narrow startDate/endDate to shrink this result." });
-		const opts = {};
-		if (loggedOnly !== void 0) opts.loggedOnly = loggedOnly;
-		if (limit !== void 0) opts.limit = limit;
-		return jsonResult(selectWorkouts(presentAthleteWorkouts(workouts), opts), { hint: "Large? Set loggedOnly:true, pass limit, or narrow startDate/endDate." });
-	}));
+	}, (args) => runAthleteWorkouts(ctx, args));
 	server.registerTool("athlete_exercises", {
 		title: "Search logged exercises",
 		description: ATHLETE_EXERCISES_DESC,
@@ -1161,7 +1189,7 @@ function registerExerciseTools(server, ctx, userId) {
 	}));
 	server.registerTool("athlete_personal_records", {
 		title: "Exercise personal records",
-		description: "The all-time PR board for an exercise (reps/weight per rep-max, strength-standard filters). Get the exercise id from athlete_exercises. For a point-in-time snapshot use athlete_exercise_stats; for the dated session trend use athlete_exercise_history.",
+		description: "The all-time PR board for an exercise (reps/weight per rep-max, strength-standard filters). Get the exercise id from athlete_exercises. A lift is often logged under several name variants, each with its own board, so if a PR looks missing check the other variants. For a point-in-time snapshot use athlete_exercise_stats; for the dated session trend use athlete_exercise_history.",
 		inputSchema: { exerciseId: idParam },
 		annotations: READ
 	}, ({ exerciseId }) => attempt(async () => jsonResult(await fetchPersonalRecords(ctx.client, toId(exerciseId)))));
@@ -1265,7 +1293,7 @@ function registerAthleteTrainingTools(server, ctx) {
 }
 //#endregion
 //#region package.json
-var version = "0.6.2";
+var version = "0.6.3";
 //#endregion
 //#region src/server.ts
 async function main() {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@trainheroic-unofficial/athlete-mcp",
-  "version": "0.6.2",
+  "version": "0.6.3",
   "license": "MIT",
   "repository": {
     "type": "git",
@@ -21,8 +21,8 @@
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
     "zod": "^4.4.3",
-    "@trainheroic-unofficial/core": "0.6.2",
-    "@trainheroic-unofficial/js": "0.6.2"
+    "@trainheroic-unofficial/core": "0.6.3",
+    "@trainheroic-unofficial/js": "0.6.3"
   },
   "devDependencies": {
     "@types/node": "^26.0.0",