Skip to main content
Glama

calc_tdee

Read-only

Compute BMR, TDEE, and recommended daily calories from client stats.

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": {
      "gender": "<gender>",
      "weightKg": "<weightKg>",
      "heightCm": "<heightCm>",
      "age": "<age>"
    },
    "name": "calc_tdee"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYes
goalNoMAINTAIN
genderYes
activityNoMODERATE
heightCmYes
weightKgYes
bodyFatPctNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds only that three derived values are produced; it does not say that goal and activity alter the calorie recommendation, whether bodyFatPct changes the formula used, or how defaults are applied. For a 7-parameter calculation tool this is thin beyond the structured data.

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 front-loaded sentence with no filler. It is efficient, though the brevity contributes to the specification gaps elsewhere rather than being a virtue on its own.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 7 parameters, 0% schema coverage, and no output schema, the description has to explain both inputs and returned values. It names the outputs but not their structure (single object? per-macro? units?) and says nothing about how the optional parameters change the calculation, leaving an agent with substantial gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but 'client stats' is vague. It never mentions goal, activity level, or bodyFatPct and gives no hint that activity drives the TDEE multiplier or that goal adjusts the calorie target. The enum values exist in the schema but their effect on the result is undocumented.

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?

The description names specific verbs and outputs (BMR, TDEE, recommended daily calories) computed from client stats, which distinguishes it from siblings like calc_1rm and calc_macros. It relies on unexplained acronyms, but the resource and scope are clear enough for an agent to identify the tool.

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?

There is no when-to-use guidance, no statement of prerequisites, and no routing to alternatives (e.g., calc_macros for macro splits). The agent must infer all context from the name and sibling list.

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.