Bodywise Fitness and Nutrition

Strength standards calculator

strength_standards_calculator

Read-onlyIdempotent

Level (Beginner to Elite) for a squat, bench press, deadlift or overhead press from a set's weight and reps and bodyweight, using lift-to-bodyweight multiples.

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": {
      "lift": "<lift>",
      "sex": "<sex>",
      "bodyweight_kg": "<bodyweight_kg>",
      "load_kg": "<load_kg>",
      "reps": "<reps>"
    },
    "name": "strength_standards_calculator"
  }
}

Input Schema

Name	Required	Description
`sex`	Yes	male or female.
`lift`	Yes	Lift.
`reps`	Yes	Reps done with that weight.
`load_kg`	Yes	Weight lifted, kg.
`bodyweight_kg`	Yes	Bodyweight in kg.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful context by identifying the method (lift-to-bodyweight multiples) and output (Level Beginner to Elite), but it does not explain how reps are incorporated or detail the return format beyond a categorical level.

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 a single efficient sentence with no wasted words, and the main purpose is front-loaded. However, the sentence is dense and could be slightly more structured for readability, preventing a perfect score.

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 rich input schema (100% coverage) and annotations covering safety, the description provides sufficient context for a calculator tool. It states the output (Level) and method, though it does not elaborate on edge cases (e.g., rep range limits) already covered by the schema. An agent can correctly invoke it without further information.

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 all five parameters (sex, lift, reps, load_kg, bodyweight_kg) are already documented in the schema including enums and bounds. The description lists the lift options and mentions weight, reps, and bodyweight, but adds no semantic detail beyond what the schema provides. Baseline 3 is appropriate.

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?

The description states a specific verb (computes Level) and resource (squat, bench press, deadlift, overhead press) with inputs (set weight, reps, bodyweight). It clearly distinguishes the output as a level (Beginner to Elite), but does not explicitly differentiate from siblings like strength_to_bodyweight_calculator or 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 Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance is provided. The description implies usage for assessing strength level from a set, but it does not name alternatives (e.g., one_rep_max for 1RM estimation) or state any prerequisites or exclusions.

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

All Bodywise Fitness and Nutrition tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?