openGym MCP Bridge

get_workout_progress

Read-onlyIdempotent

Retrieves actual exercise occurrences, completed working sets, best load, and volume split by weight basis for a specified exercise ID, enabling progress tracking without unit conversions.

Instructions

Read actual exercise occurrences, completed working sets, best load and volume split by weight basis; no conversions.

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": {
      "exercise_id": "<exercise_id>"
    },
    "name": "get_workout_progress"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No
`from`	No
`limit`	No
`offset`	No
`exercise_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds the notable trait that values are returned in the stored weight basis with no unit conversion, which is genuinely useful context. It says nothing about pagination behavior or result ordering, but with annotations doing the heavy lifting a 3 is fair.

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?

A single dense sentence that front-loads the verb and the returned data, with no filler. It is jargon-heavy but every clause carries content.

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

Completeness3/5

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

With no output schema the description must describe return values, and it partially does by naming the metrics returned. However, for a 5-parameter, 0%-coverage schema with date range and pagination inputs, the definition leaves too much to inference about scoping and paging.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description must compensate — but it says nothing about exercise_id being required, the date format implied by from/to, or the role of limit/offset. The 'by weight basis' phrase is the only parameter-adjacent insight and it is indirect.

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?

States a specific verb ('Read') and a concrete set of returned metrics: exercise occurrences, completed working sets, best load, volume split by weight basis. An agent can tell this is a progress/analytics read tool, though it is not explicitly distinguished from the closely related sibling get_exercise_history.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no alternatives named despite numerous plausible siblings (get_exercise_history, get_summary, get_weekly_training_summary). The only guidance-like clause is 'no conversions', which is a behavioral constraint rather than usage routing.

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