Skip to main content
Glama

warmup_calculator

Read-onlyIdempotent

Calculate a barbell warmup ramp for any lift. Returns a structured set of warmup sets leading up to the work weight, with decreasing reps as weight increases. Based on standard barbell warmup methodology used in Starting Strength coaching. Powered by CoachSync.io.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
liftTypeYesThe lift being warmed up for (e.g. squat, bench, press, deadlift)
barWeightNoBar weight. Defaults to 45 lb (20 kg). Use 35 for a women's bar, 15 for a training bar.
workWeightYesThe target work set weight in pounds (or kg if unit is kg)
roundingIncrementNoRound warmup weights to this increment. Default 5.

TDQS

A3.9/5.0
Behavior4/5

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

With annotations indicating read-only, idempotent, and non-destructive behavior, the description adds behavioral context about returning a structured set with decreasing reps. It does not disclose output format or edge cases, but this is acceptable for a simple calculation tool.

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?

Two sentences efficiently convey purpose and methodology, though the 'Powered by CoachSync.io' is minor fluff. Well-structured and front-loaded.

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?

Given the simplicity of a calculator tool and no output schema, the description adequately explains what the tool does and how the warmup ramp is structured. It could mention the return format but is sufficient.

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?

Schema coverage is 100%, so the description does not need to explain parameters. It adds no new semantic detail beyond the schema, meeting the baseline.

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 it calculates a barbell warmup ramp for any lift, distinguishing it from sibling tools that generate programs or load plates.

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 warming up before a work set but does not provide explicit when-to-use, when-not-to-use, or comparisons with siblings like novice_lp_generator or plate_loader.

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.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool serves a clearly distinct purpose: program generation, plate calculation, and warmup calculation. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent pattern: noun_verb in snake_case, each ending with '-er' (generator, loader, calculator). Conventions are uniform.

Tool Count4/5

With 3 tools, the set is on the smaller side but still covers core functionality for a barbell training assistant. The tools are well-scoped and non-redundant.

Completeness4/5

The set covers program generation, plate loading, and warmup calculation—core tasks for a Starting Strength coach. Minor gaps like progress tracking or deload calculation are absent but not critical for the stated purpose.

Resources