Skip to main content
Glama

Fitness Tools

by io.github.almostjacked

Powerlifting Meet Attempts

powerlifting-attempts
Read-onlyIdempotent

Deterministic opener/second/third attempts from an estimated 1RM, plus a warmup ramp and per-side plate loading. Tunable by aggressiveness and available plates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bar_weightNo
one_rep_maxYes
aggressivenessNostandard
available_platesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitYes
warmupsYes
attemptsYes
bar_weightYes
aggressivenessYes

TDQS

A3.9/5.0
Behavior4/5

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

Beyond annotations (readOnly, idempotent), description adds determinism and outputs (warmup, plate loading). No contradictions.

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

Conciseness5/5

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

Two sentences, front-loaded with key output, no extraneous words.

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 output schema and annotations, description covers main outputs and safety traits. Adequate for a read-only deterministic tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%; description mentions aggressiveness and available plates but not bar_weight or one_rep_max structure. Incomplete for 4 parameters.

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?

Description clearly states deterministic opener/second/third attempts from 1RM, plus warmup and plate loading. Distinguishes from sibling tools like one-rep-max.

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?

Implied usage for meet attempt calculation but no explicit guidance on when to use vs alternatives or prerequisites.

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

All Fitness Tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct fitness metric or calculation method, e.g., TDEE via formula vs. data, body fat via different protocols, strength, muscle mass, etc. There is no overlap that would confuse an agent.

Naming Consistency5/5

All tool names follow a consistent lowercase-with-hyphens pattern (e.g., adaptive-tdee, one-rep-max, powerlifting-attempts). The naming clearly conveys the purpose without mixing styles.

Tool Count5/5

10 tools cover a comprehensive set of fitness calculations without being excessive. Each tool earns its place, and the number is well-scoped for the domain.

Completeness5/5

The tool surface covers major fitness estimation needs: TDEE (two methods), body fat, FFMI, macros, muscle potential, strength (1RM, attempts), and sarcopenia screening. No obvious gaps for calculation-oriented fitness tools.

Resources