Skip to main content
Glama
Garmin Health MCP

Garmin Health MCP

by EmilbMadsen

get_hydration

Read-only

Retrieve daily logged water intake for a date range from Garmin Connect to track hydration trends; returns empty when no hydration is logged.

Instructions

Logged water intake per day. Empty if the user does not log hydration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hydration"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNoLast date (YYYY-MM-DD), inclusive. Default: today.
start_dateNoFirst date (YYYY-MM-DD), inclusive. Default: 6 days before end_date.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that the result is empty when the user has no hydration logs — but says nothing about units (ml vs oz), aggregation across multiple entries in a day, or timezone handling for 'today'.

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?

Two short sentences, front-loaded with the data domain and followed by the empty-result edge case; nothing is padded. It is telegraphic enough that the retrieval action itself is only implied by the tool name.

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?

An output schema exists, so return structure need not be described. However, for a metric tool with default-null date range, the absence of units, per-day aggregation rules, and timezone semantics leaves real gaps for correct interpretation of results.

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 description coverage is 100%: both start_date and end_date carry YYYY-MM-DD format, inclusivity, and default behavior, so the schema does the heavy lifting. The description adds no date semantics beyond that, which is the expected baseline when coverage is complete.

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 resource (water intake) and its granularity (per day), which distinguishes it from siblings like get_food_logs or get_daily_summaries. The verb is carried by the name rather than the description ('Logged water intake per day' is a noun phrase), so it is clear but not an explicit verb+resource statement.

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?

No statement of when to call this versus related siblings (e.g., get_daily_summaries, which may also surface hydration). The only usage-adjacent detail is the empty-result condition, which is about outcome rather than tool selection. An agent must infer the use case from the name alone.

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