Skip to main content
Glama

add_hydration_data

Record daily water intake in Garmin Connect by logging a hydration amount in milliliters with a specific date and timestamp. Use it to track fluid consumption accurately.

Instructions

Add hydration data

    Args:
        value_in_ml: Amount of liquid in milliliters
        cdate: Date in YYYY-MM-DD format
        timestamp: Timestamp in YYYY-MM-DDThh:mm:ss.sss format
    

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": {
      "value_in_ml": "<value_in_ml>",
      "cdate": "<cdate>",
      "timestamp": "<timestamp>"
    },
    "name": "add_hydration_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
cdateYes
timestampYes
value_in_mlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write with openWorldHint, so the basics are covered structurally. The description adds nothing beyond that: it does not say whether repeat calls create duplicate entries, whether data is merged with an existing day's record, or what happens on malformed dates.

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 is short and front-loads the action, with a compact Args block that is easy to scan. The parameter list is arguably redundant with the schema titles, but it is the only place the formats appear, so it earns its space.

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 three-required-parameter mutation tool with no output schema, the description covers the inputs adequately but says nothing about the result of a successful call (a created record, an updated daily total, or an error shape). An agent can call it, but cannot predict or verify the outcome from the definition.

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 description coverage is 0%, so the description carries the full burden and does so reasonably well: it names all three parameters and gives units (milliliters) and concrete string formats (YYYY-MM-DD and YYYY-MM-DDThh:mm:ss.sss). What it lacks is any constraint on value ranges or whether timestamp must match cdate, but the format documentation is a real gain over the bare schema.

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 states a specific verb and resource ("Add hydration data"), which is unambiguous for an agent. It does not distinguish itself from the read-side sibling get_hydration_data or clarify how it relates to other add_* logging tools, but the core action is clear.

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?

There is no guidance on when to use this tool versus get_hydration_data or any other logging tool, and no stated preconditions or exclusions. The agent must infer usage entirely from the name.

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

Deploy Server

Other Tools