Skip to main content
Glama

Body Fat Percentage

body-fat
Read-onlyIdempotent

Estimate body-fat % via US Navy circumference, Jackson-Pollock 3-site skinfold, and Deurenberg (BMI-based) methods.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNo
hipNo
sexYes
neckNo
waistNo
heightNo
weightNo
methodsNoall
skinfold_sumNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsYes
skippedYes
consensusYes

TDQS

B3.4/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, which cover safety. The description ('estimate') aligns with these annotations but adds no additional behavioral context beyond the structured fields.

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?

Single sentence is concise and front-loaded with purpose. However, listing methods without parameter mapping sacrifices some clarity for brevity.

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

Completeness2/5

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

Despite having an output schema, the tool has 9 parameters and multiple methods. The description fails to explain how to choose a method based on available inputs or what the output contains, leaving significant gaps for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet description only mentions method names without clarifying which parameters (e.g., waist, neck, hip for US Navy; skinfold_sum for Jackson-Pollock; age, weight, height for Deurenberg) are required for each. This leaves the agent to guess parameter usage.

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?

Description specifies the tool estimates body-fat percentage and lists three distinct methods (US Navy circumference, Jackson-Pollock 3-site skinfold, Deurenberg BMI-based). It is a specific verb+resource, and no sibling tool overlaps with this function.

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 description implies the tool is used for body-fat estimation via given methods, but provides no explicit guidance on when to use each method, prerequisites, or when alternatives (e.g., other anthropometric calculators) may be more appropriate.

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.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct fitness metric or calculation method, e.g., TDEE via formula vs. data, body fat via different protocols, strength, muscle mass, etc. There is no overlap that would confuse an agent.

Naming Consistency5/5

All tool names follow a consistent lowercase-with-hyphens pattern (e.g., adaptive-tdee, one-rep-max, powerlifting-attempts). The naming clearly conveys the purpose without mixing styles.

Tool Count5/5

10 tools cover a comprehensive set of fitness calculations without being excessive. Each tool earns its place, and the number is well-scoped for the domain.

Completeness5/5

The tool surface covers major fitness estimation needs: TDEE (two methods), body fat, FFMI, macros, muscle potential, strength (1RM, attempts), and sarcopenia screening. No obvious gaps for calculation-oriented fitness tools.