Bodywise Fitness and Nutrition

Race fuelling and hydration planner

race_fuelling_planner

Read-onlyIdempotent

Carbohydrate per hour (with glucose:fructose split), gels, fluid and sodium per hour, and a timed race schedule for runs, ultras and triathlons up to Ironman.

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>"
    },
    "name": "race_fuelling_planner"
  }
}

Input Schema

Name	Required	Description	Default
`gut`	No	Gut training: new (60 g/h cap), regular (90) or trained (120).	regular
`event`	No	Event type; sets a default duration.	marathon
`minutes`	No	Expected finish time in minutes. Defaults to the event's typical time.
`weather`	No	Race-day weather.	mild
`saltiness`	No	How salty your sweat is.	typical
`gel_carb_g`	No	Carbohydrate per gel, grams.
`bodyweight_kg`	Yes	Bodyweight in kg.
`sweat_rate_ml_per_h`	No	Measured sweat rate in ml/h, if known.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 1, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this is a pure, idempotent, closed-world read, so safety behavior needs no restating. With no output schema, the description does add value by enumerating the produced artifacts (carbs/h, gels, fluid, sodium, schedule), but it gives no units, format, or how gut-cap and sweat-rate inputs shape the result.

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?

A single dense sentence that front-loads the primary output (carbs/h) and then enumerates secondary outputs and applicable events. No filler, nothing repeated from structured fields.

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 an 8-parameter calculator with no output schema, the description should say more about what comes back — units (ml/h, mg/h), whether the schedule is split by aid-station segments, and how unknown sweat rate is defaulted. The output listing is a good start but not sufficient detail for an agent to act on the result.

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% with descriptive enums (gut caps at 60/90/120 g/h, event defaults, sweat rate range), so the schema carries the semantics. The description only loosely echoes that by mentioning the glucose:fructose split and sodium per hour, adding little beyond what the schema states.

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 the concrete outputs (carbs/h with glucose:fructose split, gels, fluid, sodium/h, timed schedule) and the targeted sports (runs, ultras, triathlons up to Ironman), which clearly separates it from siblings like carbohydrate_calculator or race_time_predictor. It lacks an explicit verb (e.g. 'computes/plans') but the resource and scope are unmistakable.

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?

The scope 'for runs, ultras and triathlons up to Ironman' implies when it applies, but there is no explicit routing — nothing says to use this instead of carbohydrate_calculator for a simple carb target, or alongside race_time_predictor for pacing. Usage is inferable rather than stated.

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

All Bodywise Fitness and Nutrition tools Inspect

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

Need Help?