openGym MCP Bridge

list_workouts

Read-onlyIdempotent

Retrieve workout history by inclusive local date range with stable IDs and paged results. Reuse cursors with identical filters; restart if history changes.

Instructions

Read-only history by inclusive local date range. Returns stable workout IDs and bounded pages. Reuse cursor with identical filters; restart if history changes.

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": "list_workouts"
  }
}

Input Schema

Name	Required	Description	Default
`to`	No
`from`	No
`limit`	No
`cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive semantics, yet the description adds real behavioral detail beyond them: bounded page sizes, stable IDs across pages, and the cursor invalidation rule when history changes. It stops short of describing return shape or error behavior on a stale cursor.

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?

Three short sentences, each earning its place: scope first, output characteristics second, cursor caveat last. No filler or repetition of the name.

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 simple 4-parameter list tool with annotations covering the safety profile, this is close, but with no output schema and no parameter descriptions the agent still lacks date string format and limit behavior. Stale-cursor failure handling is implied but not stated.

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?

With 0% schema description coverage, the schema documents nothing, so the description carries the burden. It adds real meaning for from/to (inclusive, local date semantics) and cursor (must pair with identical filters), but says nothing about date format despite maxLength 10, and only hints at limit via 'bounded pages' without noting the default of 20 or cap of 50.

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

Purpose3/5

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

The description conveys scope ('read-only history by inclusive local date range') and output character ('stable workout IDs and bounded pages'), but never names the resource explicitly or gives a verb like 'list workouts' — the tool name does that work. It also does not distinguish itself from sibling get_recent_workouts, leaving ambiguity about which to call.

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 concrete pagination guidance ('Reuse cursor with identical filters; restart if history changes'), which is genuinely useful operational advice. However, there is no guidance on when to use this versus get_recent_workouts or get_workout, and no preconditions for the date range.

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