Skip to main content
Glama

Water intake calculator

water_intake_calculator
Read-onlyIdempotent

Daily water intake for an adult woman or man from the European and US reference values, including pregnancy and breastfeeding, and how much of it usually comes from drinks. With weights before and after an exercise session, also how much to drink after it.

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": {
      "sex": "<sex>"
    },
    "name": "water_intake_calculator"
  }
}

Input Schema

NameRequiredDescriptionDefault
sexYesfemale or male; the equations and reference values differ by sex
stageNoOptional, for women
after_kgNoWeight after the same session in kilograms, 25 to 400
after_lbNoWeight after the same session in pounds, instead of after_kg
before_kgNoWeight before an exercise session in kilograms, 25 to 400
before_lbNoWeight before an exercise session in pounds, instead of before_kg

Output Schema

NameRequiredDescriptionDefault
noteNoA line instead of a number, when no number applies
pageYes
toolYes
inputsYesThe inputs as understood, in metric units
methodYesHow the answer is worked out
resultNo
disclaimerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sex / description
      Added value: +"female or male; the equations and reference values differ by sex"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds real domain context: reference values come from European and US sources, equations differ by sex, pregnancy and breastfeeding are supported, and part of the total is attributed to drinks — none of which is recoverable from the annotations. It stops short of saying how the two reference datasets are combined or whether the result is a single figure or a range, which keeps it off a 5.

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?

Two sentences, no filler, main use case front-loaded and the secondary exercise scenario second. The somewhat elliptical phrasing of the second sentence ('also how much to drink after it') is compact rather than confusing, and every clause maps to a capability or parameter group.

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?

With an output schema present the description need not explain return values, and 100% parameter coverage means the schema handles the details. What remains slightly under-specified is the interaction between the four weight parameters — whether all four can be supplied, and what happens if only before_kg is given — but the description is otherwise adequate for a six-parameter calculator.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns more by explaining why sex matters ('the equations and reference values differ'), that stage applies only to women, and that the before/after weights belong to one exercise session. That framing tells an agent these parameters are paired and conditional, which the flat schema does not convey on its own.

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 names a specific resource (daily water intake) plus the population and the source of the reference values, and it covers both the baseline and post-exercise variants. It is unmistakably distinct from bmi_calculator, calorie_calculator and protein_calculator — an agent could pick this tool without inspecting any schema.

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 rather than stated: the opening sentence signals the baseline-intake case and the closing sentence signals the exercise-rehydration case, but there is no explicit 'use this when' or 'do not use when', and no alternatives are named. The two modes are discoverable from the prose, which is the definition of implied usage.

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