Skip to main content
Glama

fitpulse

Access evidence-based workout programming, nutrition science, supplement efficacy analysis, injury recovery, and race training plans via a single API.

Instructions

FitPulse: Global fitness intelligence API. Evidence-based workout programming, nutrition science, supplement efficacy analysis, injury recovery protocols, race training plans, sleep optimization, plateau-breaki

Coverage: Global

Endpoints: • workout ($0.10): Custom workout plan • exercise ($0.08): Exercise form guide • nutrition ($0.10): Macro and nutrition targets • supplement ($0.08): Evidence-based supplement analysis • recover ($0.10): Injury recovery protocol • supplements ($0.08): Evidence-graded supplement efficacy tier list by goal • rehab ($0.10): Sports medicine rehabilitation protocol • sleep ($0.08): Athletic sleep optimization and CBT-I protocol • plateau ($0.10): Training plateau analysis and breakthrough protocol • race ($0.10): Race training plan built backwards from event date

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDays per week (default: 4)
goalNoe.g. muscle-gain, fat-loss, strength, endurance, general-fitness
langNolang
issueNoSleep issue (e.g. trouble falling asleep, early waking, poor recovery despite sleep, jet-lag)
levelNolevel
sportNoTarget sport or activity for return-to-sport phase
actionYesWhich endpoint to call. Options: workout | exercise | nutrition | supplement | recover | supplements | rehab | sleep | plateau | race
budgetNoMonthly budget for supplements (e.g. $50, $100, $200)
injuryNoe.g. sprained-ankle, pulled-hamstring, rotator-cuff, shin-splints, runners-knee
weightNoBody weight in lbs
activityNoactivity
durationNoHow long the plateau has lasted (e.g. 6 weeks, 3 months)
exerciseNoe.g. barbell-squat, push-up, romanian-deadlift, pull-up
equipmentNoe.g. full gym, dumbbells-only, bodyweight (default: full gym)
race_dateNoRace date (YYYY-MM-DD) — plan is built backwards from this date
race_typeNoRace type (5K, 10K, half-marathon, marathon, triathlon-sprint, triathlon-olympic, ironman, OCR)
restrictionsNoDietary restrictions or intolerances (vegan, lactose-free, etc.)
fitness_levelNoPre-injury fitness level (recreational, competitive, elite)
runs_per_weekNoAvailable training days per week
current_fitnessNoCurrent fitness level and recent training context
current_routineNoBrief description of current training and diet approach
training_scheduleNoTraining schedule context (e.g. morning workouts, evening training, two-a-days)
Behavior2/5

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

No annotations are provided, and the description only mentions endpoints and pricing, without disclosing behavioral traits such as rate limits, idempotency, or potential side effects. The description does not compensate for missing annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a heading and bullet list, but it is somewhat lengthy and includes pricing information that may be irrelevant for an AI agent. It could be more concise.

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

Completeness2/5

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

With 22 parameters and no output schema or annotations, the description lacks guidance on how parameters relate to specific endpoints, and does not provide sufficient context for the AI agent to use the tool effectively.

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?

The input schema has 100% coverage with parameter descriptions, so the schema already provides meaning. The tool description adds value by grouping endpoints and indicating their purpose, but does not significantly enhance parameter understanding beyond the schema.

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 clearly states 'Global fitness intelligence API' and lists endpoints covering various fitness domains, indicating a fitness-focused tool. However, it does not explicitly differentiate from sibling tools, though the sibling names suggest different domains.

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

Usage Guidelines3/5

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

The description implies usage for fitness-related queries through its content and endpoint list, but lacks explicit guidance on when to use this tool versus alternatives or any exclusions.

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/GTCC777/mcp-pulsenetwork'

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