Skip to main content
Glama
omnioperand-mcp

omnioperand-mcp

omni_one_rep_max

Calculate estimated one-rep max and 95%/85%/70% working loads from lifted weight and reps completed using Epley, Brzycki, and Lander formulas.

Instructions

One Rep Max (1RM) Calculator. Calculate estimated 1RM and percentage load working sets (95%, 85%, 70%) using Epley, Brzycki, and Lander lifting equations. Discipline: HEALTH. Governing mathematical model / formula: 1RM (Epley) = Weight × (1 + Reps / 30) | 1RM (Brzycki) = Weight / (1.0278 - 0.0278 × Reps).

USAGE GUIDELINES:

  • WHEN TO USE: Invoke for deterministic calculation of one_rep_max (Estimated 1RM (Epley)), brzycki_max (Brzycki Formula Estimate), load_85pct (85% 1RM Working Load (5-Rep)), load_70pct (70% 1RM Hypertrophy Load (12-Rep)) using weight_lifted (Lifted Weight in lbs), reps_completed (Repetitions Completed in reps). Guarantees exact machine floating-point precision, eliminating LLM arithmetic mistakes and formula hallucinations.

  • WHEN NOT TO USE: Do not use for qualitative evaluations or unquantified reasoning. All input parameters must be valid numerical values.

  • SIBLING ROUTING: Use this dedicated specialist tool for 'One Rep Max (1RM) Calculator' rather than generic dispatchers like omni_universal_query. For cross-discipline dynamic dispatch, see omni_universal_query.

BEHAVIOR & SAFETY:

  • Pure deterministic computation with machine floating-point precision.

  • Read-only, idempotent, and stateless. Zero side effects or persistent state mutations.

  • Input validation: All arguments are validated against physical and domain bounds. Out-of-bounds inputs return a safe diagnostic error status without throwing runtime exceptions.

RETURNS:

  • Structured JSON object containing:

    • status (string): "success" on valid execution or "error" if validation fails

    • calculator (string): "one-rep-max"

    • category (string): "health"

    • name (string): "One Rep Max (1RM) Calculator"

    • formula (string): Governing mathematical formula string

    • inputs (object): Echoed input parameter dictionary with applied defaults

    • metrics (object): Dictionary of computed outputs:

      • metrics.one_rep_max (Estimated 1RM (Epley)): Formatted display string (e.g. '262.5 lbs')

      • metrics.brzycki_max (Brzycki Formula Estimate): Formatted display string (e.g. '253.1 lbs')

      • metrics.load_85pct (85% 1RM Working Load (5-Rep)): Formatted display string (e.g. '223.1 lbs')

      • metrics.load_70pct (70% 1RM Hypertrophy Load (12-Rep)): Formatted display string (e.g. '183.8 lbs')

    • execution_time_ms (number): Latency in milliseconds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "omni_one_rep_max"
  }
}

Input Schema

NameRequiredDescriptionDefault
weight_liftedNoLifted Weight (lbs). Weight lifted during set. Default: 225. Min: 20. Max: 1000.
reps_completedNoRepetitions Completed (reps). Reps performed before failure (1-10 most accurate). Default: 5. Min: 1. Max: 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations supplied, the description fully carries behavioral disclosure: deterministic computation, read-only, idempotent, stateless, zero side effects, input validation against physical bounds, and safe diagnostic errors without runtime exceptions. This is unusually thorough for an annotation-free 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?

The description is structured with clear sections and front-loads purpose. It is somewhat verbose in listing every return field and example value, but the detail is useful given the absence of an output schema and annotations.

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

Completeness5/5

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

For a simple two-parameter deterministic calculator with no annotations or output schema, the description covers purpose, usage, behavior, formulas, and return structure completely. An agent has everything needed to invoke it correctly.

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%, so the schema already documents weight_lifted and reps_completed with units, defaults, and bounds. The description names these parameters and repeats units but adds no additional semantic guidance beyond what the schema provides.

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 states a specific verb and resource: 'Calculate estimated 1RM and percentage load working sets (95%, 85%, 70%)' using named formulas. It distinguishes itself from generic dispatchers by explicitly naming omni_universal_query and directing agent to use this specialist tool for 1RM calculation.

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

Usage Guidelines5/5

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

Provides explicit WHEN TO USE and WHEN NOT TO USE sections, plus sibling routing guidance. It names the exact parameters and outputs, and clarifies that it should be used instead of generic dispatchers for deterministic 1RM calculations.

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

Deploy Server

Other Tools