Skip to main content
Glama

Bodywise Fitness Coach

Carb loading calculator

carb_loading_calculator
Read-onlyIdempotent

Carbohydrate per day before a race (10–12 g/kg for events over 90 minutes) and the race-morning meal (1–4 g/kg).

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": {
      "bodyweight_kg": "<bodyweight_kg>",
      "minutes": "<minutes>"
    },
    "name": "carb_loading_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
windowNoLoading window.2-day
minutesYesExpected race time, minutes.
bodyweight_kgYesBodyweight in kg.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is fully covered. The description adds domain context (the g/kg bands and the 90-minute threshold) that helps interpret results, but it doesn't explain how the loading window or race duration affect the computed values.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It's a single short sentence with no filler, which is good, but it is a fragment rather than a front-loaded action statement, and the terseness comes at the cost of under-specification rather than efficiency.

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?

For a 3-parameter calculator with no output schema, the description should clarify what the tool returns (a per-day gram target, a race-morning target, or both) and how the window parameter changes it. It gives the underlying ranges but leaves the agent unable to predict the response shape or distinguish this from the other carb calculators.

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?

With 100% schema description coverage, the schema already documents bodyweight_kg, minutes, and the window enum, so baseline is 3. The description's dosing ranges add interpretive value for the outputs but say nothing about the 'window' enum options or how minutes drives the recommendation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the two outputs (daily carbs pre-race and race-morning meal) and gives the dosing ranges, so the resource is identifiable. But it is a noun phrase with no verb and no differentiation from close siblings like carbohydrate_calculator, carbohydrate_periodisation_calculator, or race_fuelling_planner, leaving the agent to infer which carb tool to pick.

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?

It implies a pre-race context via the '10–12 g/kg for events over 90 minutes' parenthetical, but there is no explicit when-to-use, when-not-to-use, or named alternative. Given the sibling list contains at least three other carbohydrate tools, the absence of routing guidance is a real gap.

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.

Resources