@trainheroic-unofficial/athlete-mcp 1.7.0 → 1.7.2

package/dist/server.mjs

@@ -338,6 +338,23 @@ const DEFAULT_RESULT_BUDGET = 6e4;
 const MARKER_RESERVE = 300;
 const DEFAULT_ARRAY_HINT = "Result was truncated to fit the size budget. Narrow it with a filter/search argument or paginate to see the rest.";
 const DEFAULT_OBJECT_HINT = "Result was truncated to fit the size budget. Request a more specific id or sub-resource.";
+/**
+* Clip an array to its first `keep` items and attach the `__truncated` marker describing what was
+* dropped. The marker is model-facing (tools instruct the model to key off `__truncated`), so its
+* shape has exactly one definition here: the size-budget path (`boundedSerialize`) and any tool
+* that deliberately caps a list (e.g. `athlete_exercises`) emit the same thing.
+*/
+function clipArray(items, keep, hint) {
+	return {
+		items: items.slice(0, keep),
+		__truncated: {
+			returned: keep,
+			total: items.length,
+			omitted: items.length - keep,
+			hint: hint ?? DEFAULT_ARRAY_HINT
+		}
+	};
+}
 /** Active budget. Overridable via TH_MCP_RESULT_BUDGET on Node; the default on workerd. */
 function resultBudget() {
 	const raw = (globalThis.process?.env)?.TH_MCP_RESULT_BUDGET;
@@ -394,16 +411,7 @@ function boundedSerialize(data, budget, hint) {
 	}
 	if (Array.isArray(data)) {
 		const k = largestPrefixCount(data.map((el) => JSON.stringify(el) ?? "null"), budget - MARKER_RESERVE);
-		const wrapped = {
-			items: data.slice(0, k),
-			__truncated: {
-				returned: k,
-				total: data.length,
-				omitted: data.length - k,
-				hint: hint ?? DEFAULT_ARRAY_HINT
-			}
-		};
-		const out = JSON.stringify(wrapped);
+		const out = JSON.stringify(clipArray(data, k, hint));
 		if (out.length <= budget) return out;
 	} else if (isPlainObject(data)) {
 		const key = largestArrayValuedKey(data);
@@ -1151,8 +1159,10 @@ function toSetResults(results) {
 * `param_2_data_N` string values plus a `param_N_made` flag.
 *
 * `mode` selects which write this is — the same endpoint serves both:
-*   - `"log"`: the values ARE a performed result, so `param_N_made` is 1 where the slot has data
-*     and the exercise `completed` flag is 1 when any set has logged data.
+*   - `"log"`: the values ARE a performed result, so `param_N_made` is 1 where the slot has reps
+*     entered (`param1`) and the exercise `completed` flag is 1 when any set is performed. A slot
+*     carrying only a weight (`param2`) with no reps is a target, not a performed set, so it stays
+*     un-made — matching the app, which shows no completion checkmark until reps are logged.
 *   - `"prescribe"`: the values are prescribed targets, written with every `param_N_made` and
 *     `completed` left at 0 so the set is not marked done. This matches what the app sends when a
 *     coach edits an athlete's prescribed reps/weight.
@@ -1197,7 +1207,7 @@ function buildExerciseSetPayload(savedWorkoutSetExerciseId, savedWorkoutSetId, w
 		if (target) {
 			p1 = target.param1 !== void 0 ? String(target.param1) : "";
 			p2 = target.param2 !== void 0 ? String(target.param2) : "";
-			made = performed && (p1 !== "" || p2 !== "") ? 1 : 0;
+			made = performed && p1 !== "" ? 1 : 0;
 		} else if (carryOver && coerceInt(existing?.[`param_${i}_made`]) === 1) {
 			p1 = existingSlotData(existing, `param_1_data_${i}`);
 			p2 = existingSlotData(existing, `param_2_data_${i}`);
@@ -1225,16 +1235,19 @@ function exerciseHasLoggedData(ex) {
 	for (let i = 1; i <= 10; i += 1) if (coerceInt(ex[`param_${i}_made`]) === 1) return true;
 	return false;
 }
-/** True when a result carries at least one non-empty param value (so it produces a performed slot). */
-function resultHasData(result) {
-	return result.sets.some((s) => s.param1 !== void 0 && String(s.param1) !== "" || s.param2 !== void 0 && String(s.param2) !== "");
+/** True when a result carries at least one set with reps entered (so it produces a performed slot).
+* A weight-only set (`param2` set, `param1` blank) is a target, not a performed result, and so does
+* not count — mirroring the `made` rule in {@link buildExerciseSetPayload}. */
+function resultHasPerformedSet(result) {
+	return result.sets.some((s) => s.param1 !== void 0 && String(s.param1) !== "");
 }
 /**
 * Whether every exercise in a saved workout set now has logged data — either written with data in
 * this call (`loggedIds`) or already carrying a performed slot. Gates the set-completion PUT: a
 * superset/circuit stays open until the last exercise is logged, so completing it on a partial log
-* does not flip its still-empty siblings to "done". An exercise written with only empty values does
-* not count (it would not be marked performed), so an all-empty log never completes the set.
+* does not flip its still-empty siblings to "done". An exercise written with no reps — empty values,
+* or a weight (`param2`) with no reps (`param1`) — does not count (it would not be marked performed),
+* so a no-reps log never completes the set.
 */
 function isSetFullyLogged(exercises, loggedIds) {
 	return exercises.every((ex) => {
@@ -1441,7 +1454,7 @@ async function writeSetResults(client, target, workouts, savedWorkoutSetId, resu
 	}
 	let setCompleted = false;
 	if (mode === "log") {
-		if (isSetFullyLogged(exercises, new Set(results.filter(resultHasData).map((r) => r.savedWorkoutSetExerciseId)))) {
+		if (isSetFullyLogged(exercises, new Set(results.filter(resultHasPerformedSet).map((r) => r.savedWorkoutSetExerciseId)))) {
 			const setBody = {
 				...buildSetCompletePayload(rawSet, exercises.map((e) => coerceInt(e.id)).filter((n) => n !== null), true),
 				...extra
@@ -1771,7 +1784,7 @@ function registerProfileTools(server, ctx, whoami, userId) {
 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_LOG_TARGETS_DESC = "The savedWorkoutSetId + savedWorkoutSetExerciseId that athlete_log_set needs, read straight off your scheduled/logged workouts in an inclusive YYYY-MM-DD window — no raw needed. This is the self-service path for logging into a COACH-SCHEDULED workout: read the ids here, then pass them to athlete_log_set. The default view is COMPACT: one row per saved set, each carrying its program/programId, the savedWorkoutSetId, and every exercise's savedWorkoutSetExerciseId with prescribed/performed values. When several workouts fall on the same day (you're on more than one program), narrow to one with program (a case-insensitive title substring, e.g. 'bodybuilding' — no id lookup needed), or programId/teamId if you have the id. raw:true returns the untouched API objects, but that blob is large and can be truncated when several workouts share a date — prefer the program filter + the default view. For reading what you actually did (not the log ids), use athlete_workouts.";
 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.";
+const ATHLETE_EXERCISES_DESC = "The exercises the athlete has logged (id + title + positional units). Call with no arguments to get the athlete's complete catalog, which often runs to several hundred entries; leave limit off when you want the whole list, since a no-q call returns everything by default. Pass q to free-text search by name (returns the top ranked matches, capped by limit, default 20). Use a returned id with athlete_exercise_history, athlete_personal_records, or athlete_exercise_stats (all of which require an exercise id). If a no-q result comes back wrapped with a __truncated marker, you passed a limit smaller than the catalog and are seeing a partial list; re-call without limit for all of it. 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, so check the others.";
 function runAthleteWorkouts(ctx, args) {
 	return attempt(async () => {
 		const workouts = await fetchAthleteWorkouts(ctx.client, args.startDate, args.endDate);
@@ -1784,6 +1797,24 @@ function runAthleteWorkouts(ctx, args) {
 		return jsonResult(selected, { hint: "Large? Set summary:true for one row per session, loggedOnly:true, pass limit, or narrow the dates." });
 	});
 }
+/**
+* Body of the athlete_exercises handler, hoisted to module scope so registerExerciseTools stays
+* under the oxlint max-lines-per-function cap (mirrors runAthleteWorkouts above).
+*/
+function runAthleteExercises(ctx, args) {
+	const { q, limit } = args;
+	return attempt(async () => {
+		const searching = q !== void 0 && q.trim() !== "";
+		const items = (searching ? await searchExerciseHistory(ctx.client, q, limit ?? 20) : await fetchExerciseHistoryList(ctx.client)).map((r) => ({
+			id: r.id,
+			title: r.title,
+			isCircuit: r.isCircuit ?? false,
+			units: exerciseUnits(r.param1Type, r.param2Type)
+		}));
+		if (!searching && limit !== void 0 && items.length > limit) return jsonResult(clipArray(items, limit, "Partial catalog: re-call athlete_exercises without limit to get all of them."));
+		return jsonResult(items, { hint: searching ? "Ranked matches for q. Omit q for the full catalog." : "The athlete's full exercise catalog. Pass q to search by name." });
+	});
+}
 /** Workouts, exercise catalog, per-exercise history/PRs/stats. */
 function registerExerciseTools(server, ctx, userId) {
 	server.registerTool("athlete_workouts", {
@@ -1804,18 +1835,10 @@ function registerExerciseTools(server, ctx, userId) {
 		description: ATHLETE_EXERCISES_DESC,
 		inputSchema: {
 			q: z.string().optional(),
-			limit: z.number().int().positive().max(200).optional()
+			limit: z.number().int().positive().optional()
 		},
 		annotations: READ
-	}, ({ q, limit }) => attempt(async () => {
-		const items = (q !== void 0 && q.trim() !== "" ? await searchExerciseHistory(ctx.client, q, limit ?? 20) : await fetchExerciseHistoryList(ctx.client)).map((r) => ({
-			id: r.id,
-			title: r.title,
-			isCircuit: r.isCircuit ?? false,
-			units: exerciseUnits(r.param1Type, r.param2Type)
-		}));
-		return jsonResult(limit !== void 0 ? items.slice(0, limit) : items, { hint: "Pass q to search by name, or limit to cap the list." });
-	}));
+	}, (args) => runAthleteExercises(ctx, args));
 	server.registerTool("athlete_exercise_history", {
 		title: "Exercise history + PRs",
 		description: ATHLETE_EXERCISE_HISTORY_DESC,
@@ -2034,7 +2057,7 @@ function registerAthleteTrainingTools(server, ctx) {
 }
 //#endregion
 //#region package.json
-var version = "1.7.0";
+var version = "1.7.2";
 //#endregion
 //#region src/server.ts
 async function main() {

package/package.json

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