macalc

calculate_tdee

Read-onlyIdempotent

Compute your total daily energy expenditure (maintenance calories) by multiplying BMR with a standard activity factor.

Instructions

Calculate Total Daily Energy Expenditure (maintenance calories) by multiplying a Basal Metabolic Rate by a standard activity factor. Inputs: bmr (basal metabolic rate in kcal — compute it first if unknown) and activity_level (see enum, from sedentary to very active). Returns TDEE in kcal/day. Read-only and deterministic. General guidance, not medical or dietary advice.

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": {
      "bmr": "<bmr>",
      "activity_level": "<activity_level>"
    },
    "name": "calculate_tdee"
  }
}

Input Schema

Name	Required	Description	Default
`bmr`	Yes	Basal Metabolic Rate in kcal
`activity_level`	Yes	Activity level

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.4.0Jul 6, 2026

changedOutput schema / (root)

Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "formula": {
-      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
-      "type": "string"
-    },
-    "reference_url": {
-      "description": "Link to a calcul2 page documenting the calculation in detail.",
-      "type": "string"
-    },
-    "result": {
-      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
-    },
-    "source": {
-      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedv0.1.4Apr 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "formula": {
+      "description": "Human-readable formula or method used (e.g. \"I=P·r·t\", \"Magnus formula\").",
+      "type": "string"
+    },
+    "reference_url": {
+      "description": "Link to a calcul2 page documenting the calculation in detail.",
+      "type": "string"
+    },
+    "result": {
+      "description": "Computed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools)."
+    },
+    "source": {
+      "description": "Authoritative source for the rule or formula (e.g. \"Article 197 CGI\", \"NF DTU 21\").",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Addedv0.1.1Apr 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, etc.), the description adds that the tool is deterministic and provides a disclaimer that it is general guidance, not medical advice.

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 two concise sentences, front-loading the purpose and listing inputs, output, and a disclaimer without any wasted words.

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?

The description explains the output (TDEE in kcal/day) and includes a disclaimer. For a simple deterministic tool with good annotations, it covers the essential context.

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 coverage is 100%, so the description adds minimal extra meaning beyond the schema's parameter descriptions. It mentions 'see enum' for activity_level but does not elaborate on the values.

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 explicitly states the tool calculates TDEE by multiplying BMR by an activity factor. It clearly identifies the verb 'calculate' and the resource 'Total Daily Energy Expenditure', distinguishing it from siblings like calculate_bmi.

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 advises to compute BMR first if unknown, providing clear context for when to use the tool. It implies usage after obtaining BMR, though it does not explicitly exclude other scenarios.

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

Deploy Server