Skip to main content
Glama

calculate_macros

Read-only

Calorie and macro calculator from a real personal trainer's rules (MTFIT): daily calories, protein, carbs and fat for fat loss / weight loss, recomp or muscle gain, with example meals and safe limits (calorie floors, capped deficits). No workout plan: use build_program for that. Metric or US units. Text plus structured JSON. Built from the rules coach Mat (MTFIT) uses with his in-person and online clients, backed by 10 years of his own training (160 to 215 lb at about 10 to 12% body fat). For adults 18+. Not medical or dietary advice. Terms: https://mtfit-mcp.mtfit-mcp.workers.dev/terms

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": {
      "goal": "<goal>",
      "age": "<age>",
      "sex": "<sex>",
      "activity": "<activity>"
    },
    "name": "calculate_macros"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesAge in years. Required. Under 18 gets no program.
sexYesFor the calorie estimate.
goalYesThe person's goal.
activityYesActivity outside training.
height_cmNoHeight in centimetres. Needed for nutrition targets. Or send height_ft and height_in.
height_ftNoHeight, feet part (US units). Use with height_in.
height_inNoHeight, inches part (with height_ft), or total height in inches if height_ft is not sent.
weight_kgNoBody weight in kilograms. Needed for nutrition targets. Or send weight_lb.
weight_lbNoBody weight in pounds (US units).
experienceNoLifting experience, for the muscle gain surplus. Default intermediate.
food_likesNoFoods the person likes, comma separated. Include 'vegetarian' or 'vegan' if that applies.
food_dislikesNoFoods to avoid, comma separated.
medical_conditionsNoPregnancy, heart condition or any other medical condition. Triggers the conservative plan.
training_days_per_weekNoWorkouts per week. Default 3.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false, so the description carries most of the behavioral burden and does it well: it discloses safety limits (calorie floors, capped deficits), a conservative-plan trigger for medical conditions, dual unit input, and the text-plus-JSON response format. Minor gap: it does not say what happens when required body metrics are omitted.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and the build_program exclusion are front-loaded, which is good, but the middle section is padded with marketing material — the 10-year training history and 160-to-215-lb body-fat anecdote — that does not help an agent invoke the tool. 'MTFIT' is repeated three times and 'fat loss / weight loss' is redundant.

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?

For a 14-parameter tool with no output schema, the description covers the essentials: output shape (text plus structured JSON), age restrictions, unit systems, and safety caps. The only meaningful omission is how optional food and experience inputs change the plan, which the schema partially covers by naming defaults.

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%, including enum meanings and the metric-vs-US unit pairing, so the baseline is 3. The description adds only the high-level note 'Metric or US units' and says nothing about how food_likes, food_dislikes, experience, or training_days_per_week influence the result beyond what the schema already states.

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?

States a specific verb+resource ('Calorie and macro calculator') and enumerates the outputs (daily calories, protein, carbs, fat) and supported goals (fat loss, recomp, muscle gain). It also explicitly distinguishes itself from the sibling build_program, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a clear exclusion and names the alternative: 'No workout plan: use build_program for that.' It also bounds scope with 'For adults 18+, not medical or dietary advice.' It does not address when to prefer get_intake_questions or adjust_program, but the primary routing decision is stated explicitly.

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