Skip to main content
Glama

generate_workout

Create a personalized workout plan based on your fitness goal, experience level, available time, and equipment. Tailor routines to target specific muscle groups or exclude certain exercises.

Instructions

Generate a complete workout plan tailored to goals and equipment.

Args: goal: Fitness goal: strength, hypertrophy, fat_loss, general_fitness, endurance experience_level: Level: beginner, intermediate, advanced duration_minutes: Available workout time in minutes equipment_available: Available equipment: barbell, dumbbells, cable, machine, bodyweight, none muscle_groups: Target muscle groups: chest, back, legs, shoulders, arms, core, cardio exclude_exercises: Exercise names to exclude

Behavior: This tool generates structured output without modifying external systems. Output is deterministic for identical inputs. No side effects. Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need structured analysis or classification of inputs against established frameworks or standards.

When NOT to use: Not suitable for real-time production decision-making without human review of results. Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNogeneral_fitness
api_keyNo
muscle_groupsNo
duration_minutesNo
experience_levelNointermediate
exclude_exercisesNo
equipment_availableNo
Behavior5/5

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

The description comprehensively covers behavioral traits including side effects, authentication, rate limits, error handling, idempotency, and data privacy. Since no annotations are provided, this fully compensates with detailed, accurate information.

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 well-structured with sections (Args, Behavior, When to use, Behavioral Transparency) and front-loaded with the core purpose. However, it contains some redundancy (e.g., side effects mentioned twice) and could be more concise.

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

Completeness3/5

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

While the description covers behavior, parameters, and usage guidelines thoroughly, it does not describe the output structure or format, which is a significant gap given the absence of an output schema. The 'When to use' section is also somewhat generic.

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 description lists 6 of 7 parameters with allowed values (e.g., goal, experience_level, muscle_groups), adding meaning beyond the schema which has 0% description coverage. However, the 'api_key' parameter is omitted, and the value sets are examples rather than exhaustive enums, slightly reducing clarity.

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 clearly states the tool generates a complete workout plan tailored to goals and equipment, with a specific verb and resource. It distinguishes from sibling tools like build_training_plan, calculate_body_composition, etc., by focusing on personalized plan generation.

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?

The description includes explicit 'When to use' and 'When NOT to use' sections, providing context for appropriate usage and cautioning against real-time production use without human review. However, the when-to-use statement is somewhat generic and does not directly contrast with each sibling tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/fitness-ai-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server