Skip to main content
Glama

Calcgrid

by com.tttkmbb
OverviewDiscussionsAdmin

TDEE Calculator

calculate_tdee
Read-onlyIdempotent

Use this when you need daily maintenance calories for an adult, or calorie targets for a mild/standard deficit or surplus. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery.

Do not use this when the person is a child, pregnant or breastfeeding, or you only need the resting rate (use bmr). What it computes: Estimates total daily energy expenditure from Mifflin-St Jeor BMR and an activity level, and derives calorie targets for maintaining, losing or gaining weight. Inputs: sex (enum); weight_kg (number, kg); height_cm (number, cm); age_years (number, years); activity_level (enum, optional). Complete JSON argument examples: {"sex":"male","weight_kg":70,"height_cm":175,"age_years":30,"activity_level":"moderate"} Outputs: bmr_kcal_per_day [kcal/day], activity_multiplier, tdee_kcal_per_day [kcal/day], mild_loss_kcal_per_day [kcal/day], loss_kcal_per_day [kcal/day], mild_gain_kcal_per_day [kcal/day], gain_kcal_per_day [kcal/day]. Formula: TDEE = BMR(Mifflin-St Jeor) × activity_multiplier; targets = TDEE ± 250 or ± 500 kcal/day Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/tdee with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/health/tdee.md

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sexYesBiological sex used to select the formula coefficients.
age_yearsYesAge in years. Unit: years.
height_cmYesHeight in centimetres. Unit: cm.
weight_kgYesBody weight in kilograms. Unit: kg.
activity_levelNoWeekly exercise level; maps to the standard activity multipliers 1.2 / 1.375 / 1.55 / 1.725 / 1.9.moderate

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
linksNo
resultYes
requestYes
sourcesNo
successYes
versionNo
freshnessNo
timestampYes
next_actionsNo
service_versionYesDeployed Calcgrid implementation version used for the result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / service_version
      Added value: +{
+  "description": "Deployed Calcgrid implementation version used for the result.",
+  "type": "string"
+}
    • changedOutput schema / required
      Previous value: -[
-  "success",
-  "request",
-  "result",
-  "timestamp"
-]New value: +[
+  "success",
+  "service_version",
+  "request",
+  "result",
+  "timestamp"
+]
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "activity_level": "moderate",
+    "age_years": 30,
+    "height_cm": 175,
+    "sex": "male",
+    "weight_kg": 70
+  }
+]
  3. Added
  4. Removed
  5. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description carries a lower burden. It adds value by disclosing the underlying formula (Mifflin-St Jeor, activity multipliers), the specific output fields, and a direct REST fallback path. No contradictions with annotations.

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?

The description is long but well-structured: usage, exclusions, inputs, outputs, formula, fallback, and docs. It is front-loaded with the core purpose. Each sentence serves a purpose; the REST fallback and docs may be slightly beyond minimum need, but they aid correctness. Not overly verbose for the tool's complexity.

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?

Given the tool's moderate complexity (5 params, 2 enums, multiple outputs), the description is thorough: it lists all output fields with units, provides a complete example, states the formula, gives a REST fallback, and links to docs. The output schema exists, so return-value details are covered; nothing an agent needs to call it correctly 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 description coverage is 100%, so the baseline is 3. The description adds a complete JSON argument example and explains the activity_level enum values with their multipliers, which enriches the schema but is not strictly necessary. This exceeds the baseline.

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 clearly states the tool computes TDEE from Mifflin-St Jeor BMR and activity level, and derives calorie targets for maintenance, loss, and gain. It explicitly distinguishes itself from calculate_bmr by saying 'use bmr' for resting rate, making it unique among many calculator siblings.

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

Usage Guidelines5/5

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

It provides explicit when-to-use ('when you need daily maintenance calories for an adult, or calorie targets for a mild/standard deficit or surplus') and when-not-to-use conditions ('child, pregnant or breastfeeding, or you only need the resting rate'), and names the alternative tool (bmr). This is textbook usage guidance.

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

All Calcgrid 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