goblingains

Generate new workouts

generate_workouts

Read-only

New workouts unlike any in the library, from our generator (no AI), as text: evolved from the library's workouts and movements (more lines, fewer, other formats) into kinds it does not hold. For one person. Nothing is saved; other ones each call. suggest_workouts and vary_workout stay close to library workouts instead.

A shortfall says what blocked it.

Input Schema

Name	Required	Description
`sex`	No	Who trains, for the weights and machine doses: "men", "women", or "mixed" (a man and a woman together: each at their own; Hyrox stations at the mixed doubles race load). Omitted when the user did not say: every line reads both, men's/women's ("9/6 kg", "12/10 kcal"). Anything but men gets only workouts with a women's weight on every loaded line. Example: "women".
`count`	No	How many workouts, at most 5. Example: 3.
`format`	No	Only this format: for_time, amrap, emom, intervals. Any when omitted. Example: "amrap".
`exclude`	No	Movement slugs or names (from find_movements) every workout must leave out. Example: ["burpees"].
`include`	No	Movement slugs or names (from find_movements) every workout must hold; fewer come back the more are named. Example: ["wallballs"].
`equipment`	No	What the athletes have, as list_equipment keys or names ("echo-bike" or "echo", "row erg", "ski erg"), one item per entry. Say "1 dumbbell" or "1 kettlebell" when there is only one: movements needing a pair (farmers carry, dumbbell bench press) are left out. Other counts are ignored ("1 echo" is the echo bike): say how many train in people. Movements needing anything else (a bench press needs a bench) are left out; runs need "running" in the list. A name matching several keys or none is an error naming them. Example: ["1 dumbbell", "box", "ski-erg"]. Omitted is a full gym.
`bodyweight`	No	False also leaves out movements needing no equipment (burpees, runs), so only the listed equipment is used. Example: false.
`minutes_max`	No	Longest estimated workout length, in minutes. Example: 25.
`minutes_min`	No	Shortest estimated workout length, in minutes. Example: 10.
`show_scores`	No	True adds a line of scores under each workout: feasibility (0-100, can it be done as written), difficulty (0-100, the chance of not finishing inside the cap), and against the workout it was made from: stimulus (0-1, CrossFit's stimulus kept, with the levers changed), work (x the seed's), mix shift (how far the work moved between movement patterns), design (0-1) and, for Hyrox workouts, race fidelity (0-1). Example: false.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 1, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, non-destructive, non-idempotent, and closed-world behavior. The description adds useful operational context: output is text, nothing is saved, each call produces other workouts, and a shortfall reports what blocked generation.

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 short and front-loads the purpose before naming alternatives. Some phrasing is fragmented and cryptic, such as 'more lines, fewer, other formats,' but it remains compact overall.

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

Completeness5/5

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

Given the rich 10-parameter schema, output schema, and annotations, the description supplies the key missing context: it generates novel text workouts, saves nothing, differs from sibling tools, and reports blockers on failure.

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 100%, so all 10 parameters are already richly documented in the schema. The description does not add parameter-level detail beyond structured fields, so the baseline of 3 is appropriate.

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?

The description states a specific resource and scope: newly generated workouts unlike any in the library, produced from the library's movements into formats it does not hold. It also distinguishes this tool from suggest_workouts and vary_workout, which stay close to library workouts.

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 clearly positions this tool against siblings by saying suggest_workouts and vary_workout stay close to library workouts instead. It does not spell out explicit when-not conditions, but the intended use is inferable from the contrast.

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

All goblingains tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?