openGym MCP Bridge

preview_custom_exercise_change

Read-onlyIdempotent

Dry-run custom exercise create or update actions before saving. Check official and custom duplicates, then return an existing match or a 10-minute proposal.

Instructions

Dry-run create/update custom exercises. ID remains stable; no deletion/media upload. Checks official and custom duplicates. Required for create: name, body_part, equipment. Full text catalogue required. Returns existing matching exercise or a 10-minute proposal.

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": {
      "actions": "<actions>"
    },
    "name": "preview_custom_exercise_change"
  }
}

Input Schema

Name	Required	Description	Default
`actions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context beyond them: no deletion or media upload, ID stability, duplicate checking against official and custom catalogues, and a 10-minute proposal return. It does not cover batching limits or idempotency nuances of the 20-action array, keeping it below a 5.

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?

Front-loaded and compact, with the dry-run nature and duplicate-checking stated first. The telegraphic sentence fragments are efficient but border on losing connectives (e.g., what 'full text catalogue required' attaches to).

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?

No output schema exists, and the description does helpfully characterize the two possible returns. However, it omits key invocation details for a nested-array tool: that updates need exercise_id, the 20-action cap, and the create/update enum branching. Adequate but incomplete for a schema-light tool.

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?

Schema description coverage is 0%, so the description must compensate; it does explain the create-required fields and that full text catalogue is required, but it omits the per-action 'type' enum semantics and the update-required exercise_id. Fields like primary_muscles, secondary_muscles, description, and the max 20 actions are entirely undocumented.

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?

Opens with a specific verb phrase, 'Dry-run create/update custom exercises,' that names both the resource and the non-committing nature of the call. It is immediately distinguishable from sibling preview tools (preview_plan_change, preview_workout_edit) and from list_custom_exercises/search_exercises.

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?

'Required for create: name, body_part, equipment' implies this preview is a prerequisite step, but the description never states the workflow explicitly or names the tool that actually commits the change. There are no exclusions or alternative-selection guidance, so an agent must infer when to choose this over search_exercises.

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