Skip to main content
Glama

calc_1rm

Read-only

Estimate a 1-rep max (Epley) and %1RM weight suggestions from a working 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": {
      "weightKg": "<weightKg>",
      "reps": "<reps>"
    },
    "name": "calc_1rm"
  }
}

Input Schema

NameRequiredDescriptionDefault
repsYes
weightKgYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The readOnlyHint and openWorldHint=false annotations already establish that this is a safe, offline computation, so the burden is lower. The one genuine addition is naming the Epley formula, which matters because 1RM estimates differ across formulas, but the description says nothing about accuracy limits at high rep counts, rounding of suggested percentages, or how many %1RM points are returned.

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 front-loaded sentence with no filler; the primary output (1-rep max) and formula precede the secondary output (%1RM suggestions).

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?

With no output schema, the description is the only place describing what comes back, and it does so only at a high level ('%1RM weight suggestions') without structure, count, or rounding. For a simple two-parameter calculator this is borderline sufficient but leaves real questions unanswered.

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 0%, so the description must carry the parameter meaning, and it only does so indirectly: 'working set' implies the weightKg and reps pair. The parameter names are self-describing (weightKg supplies units), but the description adds no guidance on valid rep ranges or interpretation beyond the exclusiveMinimum constraints already in the schema.

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 names a specific verb ('Estimate'), a specific output (1-rep max), the formula used (Epley), and a secondary output (%1RM weight suggestions) derived from a working set. It is immediately distinguishable from the calc_macros and calc_tdee siblings, which cover different calculations.

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?

Usage is only implied: 'from a working set' signals that the tool takes an already-performed set rather than a measured max, and the family of calc_* names suggests a calculation role. There is no explicit when-to-use or when-not-to-use statement and no named alternative.

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.