openGym MCP Bridge

list_workout_drafts

Read-onlyIdempotent

Retrieve paginated summaries of private workout drafts, including pending, committed, and abandoned ones, to review draft status before applying plan changes.

Instructions

Read paginated private draft summaries, including pending, committed and abandoned drafts.

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_workout_drafts"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`offset`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

B3.3/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, so the description's added value is the disclosure that results are paginated and span private drafts across three lifecycle states, which the annotations do not convey. It does not mention default page size or what a "summary" contains, but the core behavioral picture is clear.

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 front-loaded sentence with no filler; the key scope words (paginated, private, draft states) come immediately. Its brevity costs some needed detail, but as a structure it wastes nothing.

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

Completeness2/5

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

With no output schema, zero schema parameter documentation, and no mention of return shape beyond "draft summaries", an agent is left without ordering, default page size, or what fields a summary includes. For a listing tool whose siblings overlap heavily, the definition should do more to close those gaps.

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% for both limit and offset, so the schema supplies only integer types and bounds. The word "paginated" signals that these parameters page through results, but the description adds no meaning about defaults, max page behavior, or ordering, leaving most parameter semantics to be guessed.

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 ("Read ... private draft summaries") and enumerates the draft states covered (pending, committed, abandoned). It implicitly distinguishes itself from the singular get_workout_draft by calling these "summaries" of a collection, though it never names that sibling explicitly.

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?

There is no guidance on when to use this listing versus get_workout_draft, recover_workout_draft, or list_workouts. The "private" qualifier hints at scope but the agent must infer that this is the enumeration entry point and the others are per-draft retrievals.

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