Skip to main content
Glama

Hopi

by uk.co.hopi
OverviewDiscussionsAdmin

Daily water intake calculator

hopi_water_intake_calculator
Read-onlyIdempotent

Estimate a rough daily fluid target from body weight, using 30 to 35 ml per kg, plus an activity add (sedentary 0, light 250, moderate 500, active 750, very_active 1000 ml) and 500 ml more for hot conditions. Use units 'metric' (weightKg) or 'imperial' (weightStone and weightPounds). Returns a low-to-high range in litres, millilitres and 250 ml glasses. Source: https://hopi.co.uk/water-intake-calculator/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hotNoAdd 500 ml for hot conditions. Default false
unitsYes'metric' (kg) or 'imperial' (stone and pounds)
activityNoActivity level, default 'sedentary'sedentary
weightKgNoWeight in kilograms (metric)
weightStoneNoWhole stone part of weight (imperial)
weightPoundsNoPounds part of weight (imperial)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
lowMlYes
unitsYes
highMlYes
summaryYes
lowLitresYes
highLitresYes
lowGlassesYes
source_urlYesThe tool's page on hopi.co.uk (cite or open to check the figure)
highGlassesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / required
      Added value: +[
+  "highGlasses",
+  "highLitres",
+  "highMl",
+  "lowGlasses",
+  "lowLitres",
+  "lowMl",
+  "source_url",
+  "summary",
+  "units"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the underlying algorithm (30-35 ml/kg), the exact activity modifiers in ml, the 500 ml hot-weather adjustment, and the output format as a low-to-high range. This gives an agent a strong model of what the tool will return and how inputs affect it.

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?

The description packs formula, activity values, hot adjustment, unit selection, and output units into a compact, front-loaded block. The source URL is slightly extra but useful and does not bloat the text materially.

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

Completeness5/5

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

With an output schema present and annotations declaring the tool read-only and safe, the description covers the calculation logic, all relevant parameters, unit choices, and output units. Nothing an agent needs to invoke and interpret the result correctly is missing.

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%, but the description adds real meaning by connecting the units enum to the weight fields ('metric' uses weightKg, 'imperial' uses weightStone and weightPounds) and by spelling out the ml values behind each activity level. It doesn't fully explain unit conversion details, but it goes beyond the schema's plain field labels.

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 uses a specific verb and resource ('Estimate a rough daily fluid target from body weight') and gives the exact calculation basis, so an agent can identify exactly what the tool computes. It clearly distinguishes this from the many other calculator siblings by naming the formula and outputs.

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

Usage Guidelines4/5

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

The description makes the use case unmistakable: compute daily fluid intake from body weight, with metric or imperial units and optional adjustments. It doesn't explicitly name alternatives or exclusions, but among the siblings there is no competing hydration tool, so clear context is sufficient.

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

All Hopi toolsInspect
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