Skip to main content
Glama

Plan My Workout

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

A weekly workout plan with sets, reps and rest

get_workout_plan
Read-onlyIdempotent

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, but the description adds real context: days>6 is planned as 6 with a rest day and surfaced via say, plan.days_asked and plan.days_note; days=1 yields a single session; running goals return weeks of sessions. It does not discuss rate limits, auth, or failure modes, so it is strong but not exhaustive.

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?

Front-loaded with a one-sentence purpose before any examples, and every example corresponds to a real routing decision. The middle sentence is a long run-on listing of sample prompts, which makes it less scannable than it could be, but the content largely earns its place given 8 optional fields and no output schema.

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?

For an optional-parameter generator with no output schema, the description covers defaults, field-vs-q precedence, seed-based regeneration, day clamping behavior, and running-plan week structure. An agent has enough to call it correctly without further context.

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 description coverage is 100% and already documents defaults, ranges and enums, which establishes a baseline of 3. The description meaningfully adds interaction semantics the schema cannot: q is interpreted by the service but is overridden by explicit fields, and seed reuse produces a different mix of exercises with the same setup.

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?

States a specific resource and scope ('a weekly workout plan with sets, reps and rest') and anchors it with concrete request examples. It is clearly distinguishable from siblings get_exercise and list_exercises, which return individual exercises rather than a generated plan.

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?

Gives explicit when-to-use triggers across many example utterances, plus the alternative paths for input ('pass the fields, or pass the user's words in q'), the tie-break rule ('Fields win over q'), and the regeneration convention ('send the same inputs with seed plus one'). Special-case routing for 10K/running vs beginner is also spelled out.

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

All Plan My Workout toolsInspect
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