Skip to main content
Glama

Use WODs in Gymdesk in Gymdesk

gymdesk_use_wods_in_gymdesk
Read-onlyIdempotent

Use WODs in Gymdesk in the user's own Gymdesk account from ChatGPT, Claude or any AI agent. Returns how to do it in Gymdesk step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser. Gymdesk's official API: No publicly documented Gymdesk API was found on 11 Nov 2026: gymdesk.com/api, gymdesk.com/developers and docs.gymdesk.com/api returned 404 and the help center has no Gymdesk API article.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotent, non-destructive, closed-world), and the description is consistent with them. Beyond that it discloses the return content (step-by-step screens, buttons, fields) and the side-effect boundary ('opens nothing by itself'), plus the notable absence of a documented Gymdesk API, which explains why browser automation is required. Lack of any note on step detail or pagination limits keeps it from 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?

The core purpose and the no-side-effects constraint are front-loaded in the first two clauses, which is the right structure. There is some padding — 'in the user's own Gymdesk account from ChatGPT, Claude or any AI agent' and a dated API research footnote (11 Nov 2026) — that is supporting context rather than essential instruction, but it does not obscure the call decision.

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?

With no parameters and no output schema, the description carries the burden of explaining what comes back, and it does so (step-by-step instructions with screens, buttons, fields). It also explains the follow-up execution path via cotlet_browser_* tools. Complete enough for a zero-arg guidance tool.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4. The description correctly implies no input is needed beyond the topic implied by the tool name, and nothing in the schema requires further explanation.

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 states a specific verb and output: it 'Returns how to do it in Gymdesk step by step (screens, buttons, fields)' for WODs, so the agent knows this is a guidance-retrieval tool rather than an action tool. It is clear but does not explicitly contrast itself with the many action siblings (e.g. gymdesk_check_a_member_visitor_or_lead_in_to_a_session), relying on the reader to infer that those mutate state while this one only returns instructions.

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

Usage Guidelines4/5

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

It gives a usable workflow: call this to get the steps, then 'do it with the cotlet_browser_* tools in the user's Gymdesk Cloud Browser', and it states the tool 'opens nothing by itself'. That effectively routes the agent to the correct execution mechanism. It stops short of explicit when-not-to-use exclusions or naming which sibling handles WOD actions directly.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources