openGym MCP Bridge

get_recent_workouts

Retrieve recent logged workouts with set-by-set weights, reps, and optional RIR/RPE to review training history and track performance. Choose how many workouts to return, up to 20.

Instructions

Read-only. View up to 20 recent logged workouts, with set-by-set actual weights, reps and optional RIR/RPE.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does disclose 'Read-only' and the 20-item cap, which are useful. It omits ordering (most-recent-first?), what 'recent' means in time, and whether the 20 cap is fixed or filterable, leaving real gaps for a no-annotation tool.

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?

Two short clauses with zero waste, and the safety/scope signal ('Read-only', cap) is front-loaded before the payload detail.

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

Completeness4/5

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

For a one-parameter list tool with no output schema, the description adequately conveys what comes back and the size bound. Gaps around ordering, time window, and pagination keep it from being fully complete.

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

Parameters3/5

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

The single 'limit' parameter has no schema description (0% coverage), so the description must compensate. 'Up to 20' communicates the effective maximum but never mentions the parameter, its default of 10, or its 1–20 range, so it only partially covers the gap.

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 and resource ('View ... recent logged workouts') and adds the content shape (set-by-set actual weights, reps, optional RIR/RPE). It does not explicitly distinguish itself from close siblings like list_workouts or get_workout, so it lands at 4 rather than 5.

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

Usage Guidelines3/5

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

The 'recent' + 'up to 20' framing implies this is the quick-glance tool versus deeper history lookups, but no alternative is named and no when-not guidance is given. Usage is inferable from the sibling list, not stated.

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