Skip to main content
Glama

Good Turn Studio (all tools)

Plan My Workout: A weekly workout plan with sets, reps and rest

planmyworkout_get_workout_plan
Read-onlyIdempotent

Plan My Workout. A weekly workout plan with sets, reps and rest. Use for "make me a 3 day beginner gym plan", "home workout with just dumbbells, 30 minutes", "a 5 day muscle building split", "I have a pull-up bar and dumbbells", "a 20 minute workout" (days=1 gives a single session), "a workout plan to lose weight", "couch to 5K" or "a 10K running plan" (a 10K or longer goal gets the build-up plan unless the user says they are a beginner), or "give me another one" (send the same inputs with seed plus one). Either pass the fields, or pass the user's words in q and the service reads days, minutes, level, goal and equipment from them. Fields win over q. Running plans also return weeks: every week's sessions (a 9-week walk-run build to 30 minutes of running for beginners; easy, interval, tempo and long runs for intermediates), with week 1 laid out in days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoThe user's request in their own words, for example "3 day beginner gym plan, 45 minutes".
daysNoDays per week, 1 to 6 (1 gives a single session). More than 6 (or "every day") is planned as 6 with a rest day, and the answer says so in say and in plan.days_asked and plan.days_note. Default 3.
goalNostrength, muscle, general (default), conditioning (use this for fat loss or weight loss requests), running or mobility.
seedNo0 to 9999. Change it for a different mix of exercises with the same setup. Default 0.
levelNobeginner (default) or intermediate. Advanced is treated as intermediate.
countryNoTwo-letter country code for kit links (US, GB, IE, CA, AU). Defaults to the visitor's country.
minutesNoMinutes per session including warm-up, 15 to 120. Default 45.
equipmentNoComma separated: none (default), dumbbells, barbell, gym, bands, kettlebell, pullupbar (a pull-up bar), jumprope.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), so the description correctly focuses on behavioral nuances: fields winning over q, seed driving variation, and running plans emitting weeks with week 1 laid out in days. It adds real context beyond structured fields, though return shape is only loosely sketched.

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?

Purpose is front-loaded and the example-first structure is easy to scan, but the paragraph is dense with long parenthetical asides. Nearly every clause earns its place for routing, yet the run-on sentence could be tightened without losing guidance.

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 output schema, the description carries the burden of describing returns and does so at a high level (plan with sets/reps/rest; running plans add weeks). It covers all 8 parameters and their defaults, leaving only the precise output structure unspecified, which is a minor gap.

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?

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining cross-parameter semantics: days=1 yields a single session, seed+1 regenerates a variant, fields override q, and the running goal changes what weeks are returned.

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 names a specific verb+resource (generate a weekly workout plan with sets, reps and rest) and explicitly extends scope to running plans. It is clearly distinguishable from the sibling exercise-lookup tools (get_exercise, list_exercises) because it produces a full plan rather than a single movement.

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

Usage Guidelines5/5

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

It supplies concrete trigger utterances ('3 day beginner gym plan', 'home workout with just dumbbells, 30 minutes', 'couch to 5K'), states the days=1 single-session case, the 'give me another one' regeneration rule (seed+1), and the fields-over-q precedence. This is explicit when-to-use guidance with clear alternatives.

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.