Skip to main content
Glama

Hopi

by uk.co.hopi
OverviewDiscussionsAdmin

TDEE & calorie calculator

hopi_tdee_calculator
Read-onlyIdempotent

Estimate daily calories (TDEE) and BMR using the Mifflin-St Jeor equation. BMR = 10 x kg + 6.25 x cm - 5 x age + (5 for male, -161 for female). TDEE = BMR x activity factor (sedentary 1.2, light 1.375, moderate 1.55, active 1.725, very_active 1.9). Use units 'metric' (heightCm, weightKg) or 'imperial' (heightInches, weightPounds). Also returns mild-loss (-250), loss (-500) and gain (+500) calorie goals. Source: https://hopi.co.uk/tdee-calculator/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageYesAge in years
sexYesBiological sex
unitsYes'metric' (cm, kg) or 'imperial' (inches, pounds)
activityNoActivity level, default 'moderate'moderate
heightCmNoHeight in centimetres (metric)
weightKgNoWeight in kilograms (metric)
heightInchesNoTotal height in inches (imperial)
weightPoundsNoWeight in pounds (imperial)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageYes
bmrYes
sexYes
gainYes
lossYes
tdeeYes
summaryYes
activityYes
mildLossYes
source_urlYesThe tool's page on hopi.co.uk (cite or open to check the figure)
activityFactorYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / required
      Added value: +[
+  "activity",
+  "activityFactor",
+  "age",
+  "bmr",
+  "gain",
+  "loss",
+  "mildLoss",
+  "sex",
+  "source_url",
+  "summary",
+  "tdee"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as read-only and idempotent, and the description adds useful behavioral detail: the exact equation, activity multipliers, unit choices, and returned calorie-goal deltas. This goes beyond the structured annotations without contradicting them.

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?

The description is front-loaded with the core purpose, then provides the formula, unit mappings, and output goals in a logical order. Every sentence conveys necessary information, and there is no filler or repetition of schema details.

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?

The description, combined with the fully covered input schema and existing output schema, gives an agent everything needed to call this tool correctly. It explains the calculation method, unit requirements, activity options, and returned calorie goals, so no critical operational detail is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents the parameters. The description adds extra meaning by connecting heightCm/weightKg to metric and heightInches/weightPounds to imperial, and by showing how age, sex, and activity feed into the formula. This is meaningful value beyond the schema.

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?

The description states a specific verb ('Estimate'), a clear resource (daily calories/TDEE and BMR), and the exact method (Mifflin-St Jeor). It also names the output goals (mild-loss, loss, gain), making it easy to distinguish this from sibling health calculators like BMI or body-fat tools.

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?

The description makes the intended use clear: estimating TDEE and BMR with metric or imperial inputs. It does not explicitly name alternative tools or say when not to use this calculator, but the stated purpose and unit instructions provide enough context for an agent to select it appropriately.

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

All Hopi toolsInspect
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