Retrieve a single workout session with every set's weight, unit, reps, RIR, duration, notes, and targets for detailed training review.
One workout with every set: weight, unit, reps, RIR (reps in reserve), duration, notes and targets.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description contributes only the scope of what is returned (all sets with their metrics), and says nothing about failure behavior for an invalid session_id. Given the annotation coverage, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single compact sentence that front-loads the core concept ('One workout with every set') and then enumerates fields with zero filler. It is a fragment rather than a full sentence, but nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does carry the burden of describing return values, and it does so adequately by listing the per-set fields. However, it leaves the required input parameter entirely unexplained, which is a meaningful gap for a tool the agent must call with an ID.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% and the single required parameter session_id has no description in either the schema or the description. The description does not state the ID format or where to obtain a valid session_id, so it fails to compensate for the coverage gap.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The phrase 'One workout with every set' plus the enumerated fields (weight, unit, reps, RIR, duration, notes, targets) makes clear this retrieves a single session with set-level detail. The singular 'One workout' implicitly distinguishes it from the sibling get_sessions, though it never names that alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no statement of when to use this tool versus get_sessions or get_exercise_history, and no mention that it requires a session_id obtained elsewhere. The agent must infer the retrieval context from the noun phrase alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.