openGym MCP Bridge

preview_workout_log

Preview 1-10 completed workouts with real dates, valid exercise IDs, and measured sets before saving. Returns a 10-minute proposal without writing data.

Instructions

Dry-run ONLY. Preview 1-10 completed workouts using actual dates, valid exercise IDs and measured sets. Ordinary sets contain reps or seconds; unilateral reps require actual sides.L and sides.R. Optional phase, note and weight_basis preserve native meaning without converting history. Never invent missing data. Returns a 10-minute proposal; no data is written.

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": {
      "workouts": "<workouts>"
    },
    "name": "preview_workout_log"
  }
}

Input Schema

Name	Required	Description	Default
`workouts`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key safety behavior: it is a dry-run that writes no data and returns a proposal. It does not cover permission requirements, validation behavior, or response details beyond '10-minute proposal'.

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 front-loaded with 'Dry-run ONLY' and stays compact, with each sentence carrying relevant constraints. Some phrasing such as 'Returns a 10-minute proposal' is slightly ambiguous, but overall it is efficient and readable.

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?

For a complex nested input with no annotations and no output schema, the description covers the most important behavioral and validation constraints. It still leaves gaps around the full response shape, error handling, and several optional input fields.

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 description adds meaningful semantics for key nested inputs: actual dates, valid exercise IDs, reps/seconds versus unilateral sides.L and sides.R, and preserving native meaning via phase/note/weight_basis. With schema description coverage reported at 0%, it partially compensates but leaves many optional workout fields undocumented.

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 clearly states a specific verb and resource: a dry-run preview of 1-10 completed workouts. It distinguishes itself from write operations through 'no data is written', but does not explicitly distinguish itself from siblings such as preview_workout_edit.

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?

It gives useful usage constraints such as 'Dry-run ONLY', 1-10 workouts, actual dates, valid exercise IDs, and measured sets. However, it does not explicitly say when to use this preview versus sibling preview tools or when not to use it.

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