Skip to main content
Glama

Bodywise Fitness Coach

IPF GL points

ipf_gl_points_calculator
Read-onlyIdempotent

IPF GL points (IPF 2020 classic three-lift coefficients) for a squat + bench + deadlift total at a given bodyweight.

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>",
      "sex": "<sex>",
      "total_lifted_kg": "<total_lifted_kg>"
    },
    "name": "ipf_gl_points_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexYesSex assigned at birth.
weight_kgYesBodyweight in kg.
total_lifted_kgYesSquat + bench + deadlift total in kg.

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?

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so safety is covered. The description's useful addition is the coefficient variant ('2020 classic three-lift'), which tells the agent results are IPF-specific; it says nothing about precision, rounding or output format.

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 qualifying coefficient variant is placed immediately after the tool's core purpose.

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 stateless calculator with three fully documented parameters, complete annotations and no output schema, nothing an agent needs to invoke it correctly is missing; the variant qualifier resolves the only real ambiguity.

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% and bounds/enum are already declared, so the schema carries parameter meaning. The description only restates that total_lifted_kg is squat+bench+deadlift, adding no new format or constraint 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-equivalent (computes) and resource (IPF GL points) plus the coefficient variant (IPF 2020 classic three-lift) and inputs (squat+bench+deadlift total, bodyweight). An agent can tell it apart from generic lift tools, though it never names the obvious alternative scorer (dots_wilks_calculator) in the description.

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 phrase 'IPF 2020 classic three-lift' implies the applicable context (raw/classic IPF scoring rather than DOTS or Wilks), but there is no explicit when-to-use or when-not-to-use statement and no pointer to sibling scoring tools.

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