technogym-mcp

get_workout_session

Fetch every detail of a workout session: exercises, sets, reps, weight, rest, calories, MOVEs, and muscle scores. Use session_id to get comprehensive data for performance analysis.

Instructions

Full detail for one workout session: every exercise with machine, status, duration, calories, MOVEs, muscles, per-set reps / weight / rest (performed and prescribed), plus session efficacy and muscle scores. Each exercise carries an analytics_id for get_exercise_analytics.

Args: session_id: The session_id from list_workout_sessions. date: The session's ISO date. Strongly recommended; if omitted the last year of history is scanned to find it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "get_workout_session"
  }
}

Input Schema

Name	Required	Description	Default
`date`	No
`session_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the potentially expensive behavior of scanning the last year when date is omitted, and clarifies that each exercise exposes an analytics_id for downstream use. It does not explicitly state read-only or error behavior, but the 'get' verb and detail-oriented wording make the read-only nature clear.

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

Conciseness5/5

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

The description is front-loaded with the tool's purpose, enumerates the returned data compactly, and clearly separates argument explanations. Every sentence adds useful information with no filler.

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?

Given that an output schema exists, the description does not need to fully detail return values. It provides enough context for reliable selection and invocation: where the required id comes from, how the optional date behaves, and how results link to a sibling tool.

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

Parameters5/5

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

The input schema has 0% description coverage, so the description must fully compensate. It explains session_id's provenance and defines date in ISO format with the consequence of omission, adding meaningful semantics beyond the bare schema fields.

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

Purpose5/5

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

The description states a clear verb and resource: retrieving full detail for a single workout session. It enumerates exactly what is included and distinguishes itself from list/recent workouts by emphasizing 'one workout session' and the session_id, while also linking to get_exercise_analytics.

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?

It provides explicit invocation guidance: session_id comes from list_workout_sessions, and date is strongly recommended to avoid scanning a year of history. It does not explicitly describe when to prefer alternatives such as get_recent_workouts, so it misses the full 'when-not' guidance.

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

Deploy Server