Skip to main content
Glama

get_hydration_data

Read-only

Fetches hydration data for a specific date (YYYY-MM-DD) from Garmin Connect, helping you track daily fluid intake and hydration trends.

Instructions

Get hydration data

    Args:
        date: Date in YYYY-MM-DD 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": {
      "date": "<date>"
    },
    "name": "get_hydration_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered by structured data. The description adds only the date argument's format, and discloses nothing about return shape, units, or empty-day behavior — modest additional value over the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short with the resource stated up front, but the body is an auto-generated `Args:` docstring block rather than purpose-written guidance, so the space that could have carried meaningful detail is used for a single format note.

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

Completeness2/5

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

For a simple one-parameter read tool with annotations covering safety, the main remaining need is what the call returns since there is no output schema — and the description says nothing about return values, units, or empty results. It is minimally callable but not informative enough to use confidently.

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 0%, so the description must carry parameter meaning; it does specify the YYYY-MM-DD format, which the bare `{"type":"string","title":"Date"}` schema does not. However, it does not clarify whether the date selects a single day's data or acts as a range anchor, leaving the parameter only half-specified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a clear verb+resource ("Get hydration data") but says nothing about what the data contains — fluid intake totals, log entries, units, or granularity. It is adequate to distinguish a read from the sibling `add_hydration_data`, but an agent cannot tell whether this returns per-day aggregates or individual entries.

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 when-to-use guidance, no indication of how this differs from `add_hydration_data`, and no constraint on which dates are valid (past only, retention window, timezone basis). The only usage hint is the implicit need to supply a date.

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