Wellness Project

get_workout

Read-onlyIdempotent

Retrieve full detail of a workout session: exercises, sets, reps, weights, superset groupings, heart points, notes, and NSI scoring at every grain. Use for detailed questions about a past workout, reviewing training before recommendations, confirming what was logged, or comparing a session to population strength standards.

NSI: session NSI/rating in the header; per-exercise NSI (max set NSI), rating, est. 1RM, and the population_1rm_lb/population_reps benchmark it was measured against; per-set NSI and est. 1RM to see which set drove the exercise score.

EQUIPMENT: shown per exercise when every set shares a tag, else per set; missing means untagged. A wrong or missing tag on a dumbbell exercise silently halves or doubles its NSI score — fix it via update_workout's set_updates or add_exercises equipment field.

session_id: reuse an ID returned by a workout tool; unknown: list_workouts. Never guess.

SAVED WORKOUTS: pass saved_workout_id to read a reusable Saved Workout prescription. Do not combine it with session_id/session_date.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`session_id`	Yes	Session ID returned by a workout tool.
`saved_workout_id`	No	Saved Workout ID from list_workouts(saved_workouts=true). When present, returns the reusable prescription instead of a completed workout session.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes	Human-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedInput schema / properties / session_id / description

Previous value: -"Session ID from list_workouts. Required."New value: +"Session ID returned by a workout tool."

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / saved_workout_id

Added value: +{
+  "description": "Saved Workout ID from list_workouts(saved_workouts=true). When present, returns the reusable prescription instead of a completed workout session.",
+  "type": "integer"
+}

First observedAug 2, 2026

TDQS

A4.3/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the operation read-only, idempotent, and non-destructive. The description goes well beyond this by explaining NSI scoring behavior at session, exercise, and set grains, disclosing that missing/wrong equipment tags can silently alter NSI scores, and explaining how saved workout prescriptions differ from completed sessions. This is rich, honest behavioral context that an agent would otherwise have no way to infer.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is longer than average but well structured with labeled sections (NSI, EQUIPMENT, SAVED WORKOUTS) and front-loads the core purpose in the first sentence. Some detail, such as the equipment tag consequence, could arguably live in update_workout, but it is relevant here because it explains how to interpret the retrieved data. It is organized enough to remain navigable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with two parameters, rich output schema, and clear annotations, the description covers everything an agent needs: how to retrieve session details, how to interpret NSI and equipment fields, how to handle saved workouts, and how to recover from unknown IDs. There are no obvious gaps that would prevent correct invocation or interpretation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful guidance beyond the schema: session IDs should be reused from workout tool results, unknown IDs should be resolved via list_workouts, saved_workout_id returns a prescription rather than a logged session, and the two IDs should not be combined. This materially helps an agent choose and populate the parameters correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear, specific verb and resource: 'Retrieve full detail of a workout session,' and enumerates the included data fields. It differentiates itself from list_workouts and update_workout by naming them, though it does not explicitly distinguish itself from the sibling show_workout, leaving some ambiguity about how the two compare.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states when to use the tool: for detailed questions about a past workout, reviewing training, confirming logs, or comparing to population standards. It also gives clear routing guidance for unknown session IDs ('list_workouts. Never guess') and for saved workouts, including a warning not to combine saved_workout_id with session_id. It does not mention show_workout as an alternative, but the provided context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wellness Project tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.