Skip to main content
Glama

Bodywise Fitness Coach

One-rep max and working weights

one_rep_max
Read-onlyIdempotent

Estimate a 1RM (Epley, counting reps in reserve) and working weights from a completed set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "weight_kg": "<weight_kg>",
      "reps": "<reps>",
      "rir": "<rir>"
    },
    "name": "one_rep_max"
  }
}

Input Schema

NameRequiredDescriptionDefault
rirYesReps in reserve (0–4).
repsYesRepetitions completed.
weight_kgYesWeight lifted in kg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious context beyond that: the Epley formula is disclosed and RIR is explicitly folded into the estimate, which tells the agent how the number is produced. It stops short of describing the shape of the returned working weights.

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?

A single sentence with the core operation front-loaded and zero filler. Every clause (formula, RIR handling, source of data) earns its place.

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?

There is no output schema, so the description carries the burden of describing returns. It signals that a 1RM and 'working weights' come back, but never explains what working weights are (a percentage table? a set of loads?), which is the main thing an agent needs to interpret the result. Adequate but with a visible gap.

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 description coverage is 100% (each of weight_kg, reps, rir is documented with ranges), so the baseline is 3. The phrase 'counting reps in reserve' confirms how rir is consumed but adds no format or unit detail 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?

States a specific verb (Estimate) and resource (1RM plus working weights), and names the estimation method (Epley, adjusted for reps in reserve) plus the input context (a completed set). This makes it distinguishable in spirit from rpe_rir_calculator, but it never names that or any other sibling explicitly, so differentiation is left to inference.

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?

'from a completed set' implies the trigger context, i.e. use this after a set has been performed rather than to prescribe a target load. There is no explicit when-not guidance and no mention of the closest alternative (rpe_rir_calculator), so an agent must infer the routing.

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.

Resources