Skip to main content
Glama

Bodywise Fitness Coach

Body recomposition calculator

body_recomposition_simulator
Read-onlyIdempotent

Project fat loss and muscle change week by week for a chosen deficit, protein intake and training experience, with daily calorie and macro targets.

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": {
      "sex": "<sex>",
      "weight_kg": "<weight_kg>",
      "body_fat_percent": "<body_fat_percent>",
      "maintenance_kcal": "<maintenance_kcal>"
    },
    "name": "body_recomposition_simulator"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexYesmale or female.
weeksNoWeeks to simulate.
weight_kgYesBodyweight in kg.
deficit_percentNoCalories below maintenance, % (0–30).
training_statusNonew, returning, trained (1–3 years) or advanced (3+ years).new
body_fat_percentYesBody fat percentage.
maintenance_kcalYesMaintenance calories per day.
protein_g_per_kgNoProtein in g per kg bodyweight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world calculation, so the safety profile is covered. The description adds that the output is a week-by-week projection including daily calorie and macro targets, which is useful since no output schema exists, but it says nothing about the shape of that projection, unit conventions, or the model's assumptions/limits.

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?

A single sentence with no filler, front-loaded with what the tool produces and followed by the inputs that drive it. It is dense but every clause contributes; it could only be improved by a short when-to-use addendum.

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 eight parameters, no output schema and a multi-week simulation, the agent still lacks the return shape (a table? per-week rows? totals?), the assumptions of the model, and guidance on defaults like the 16-week horizon. The annotations handle safety, but the informational burden falls largely on a one-sentence description.

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% with ranges, defaults and enums documented, so the schema does the heavy lifting. The description only echoes three of the eight inputs (deficit, protein intake, training experience) and adds no interpretive meaning, such as how training_status alters the rate of muscle gain.

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?

Uses a specific verb ('Project') on specific resources ('fat loss and muscle change') at a stated granularity ('week by week'), plus the key drivers (deficit, protein, training experience). It implicitly separates itself from fat_loss_timeline_calculator by covering muscle change and training experience, but never names an alternative explicitly.

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?

The description never says when to pick this over fat_loss_timeline_calculator, lean_bulking_rate_calculator or macro_calculator, nor does it state prerequisites (e.g. that maintenance calories must be estimated first, or that this is a cutting-only scenario). An agent must infer the selection criteria from the title and inputs alone.

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