Skip to main content
Glama

calc_macros

Read-only

Compute a macro split (protein/carbs/fat in grams) for a strategy. STANDARD=40/30/30, PRO=g/kg multipliers, KETO=25/5/70.

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": {
      "calories": "<calories>",
      "weightKg": "<weightKg>"
    },
    "name": "calc_macros"
  }
}

Input Schema

NameRequiredDescriptionDefault
caloriesYes
fatPerKgNo
strategyNoSTANDARD
weightKgYes
proteinPerKgNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish this as a safe, closed-world read-only computation, so the bar is low. The description adds that the result is expressed in grams and that the strategy determines the split ratios, but it says nothing about determinism, default behavior when optional per-kg inputs are omitted, or what the response looks like.

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?

Two sentences, no filler, with the core purpose front-loaded and the strategy semantics appended. The density works against it slightly, since the enum explanations are abbreviated to the point of near-cryptic notation.

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

Completeness3/5

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

For a five-parameter tool with no schema descriptions and no output schema, the description should explain the optional per-kg inputs and confirm the return shape. It covers the strategy dimension but leaves an agent unable to reason about proteinPerKg/fatPerKg, which is the main gap.

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 0% across five parameters, so the description carries the burden and only partially meets it. It clarifies the strategy enum values and their meaning, but leaves proteinPerKg and fatPerKg entirely undocumented, and the compressed "PRO=g/kg multipliers" and "KETO=25/5/70" notation leaves the units and ordering of those ratios ambiguous.

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 a specific verb and resource ("Compute a macro split") and states the output unit (grams of protein/carbs/fat), which is more than a restatement of the name. It stops short of distinguishing itself from calculation siblings like calc_tdee or calc_1rm, so an agent must infer that this tool turns calories into macro grams.

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

Usage Guidelines3/5

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

Usage is implied by "for a strategy" plus the enumerated strategy values, but there is no explicit when-to-use or when-not guidance and no pointer to a related tool (e.g., that calories usually come from a TDEE calculation). The agent can guess the context but is given no routing signal.

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.