Skip to main content
Glama

get_hydration

Access daily hydration data from Garmin Connect. Input a date to obtain water intake records.

Instructions

Get daily hydration data (water intake)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format. Defaults to today if not provided

Implementation Reference

  • The handler function that executes the get_hydration tool logic. It calls client.getHydration(date) and returns the result as JSON text content.
    async ({ date }) => {
      const data = await client.getHydration(date);
      return {
        content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
      };
    },
  • Input schema (dateParamSchema) used by get_hydration - accepts an optional date string in YYYY-MM-DD format, defaults to today.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • Registration of the 'get_hydration' tool on the MCP server via server.registerTool() with description and input schema.
    server.registerTool(
      'get_hydration',
      {
        description: 'Get daily hydration data (water intake)',
        inputSchema: dateParamSchema.shape,
      },
      async ({ date }) => {
        const data = await client.getHydration(date);
        return {
          content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
        };
      },
    );
  • The getHydration() method on GarminClient that makes the API request to the hydration endpoint.
    async getHydration(date?: string): Promise<unknown> {
      const resolvedDate = date ?? todayString();
      return this.request(`${HYDRATION_ENDPOINT}/${resolvedDate}`);
    }
  • The HYDRATION_ENDPOINT constant defining the API endpoint path for hydration data.
    export const HYDRATION_ENDPOINT = '/usersummary-service/usersummary/hydration/daily';
Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It states the tool retrieves daily hydration data but does not specify the output format, units, or any side effects. The agent remains unaware of what the response looks like.

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 extremely concise (one sentence) and front-loaded with the key action. However, it lacks structure and fails to include necessary details, making it efficient but incomplete.

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?

Given the lack of output schema and annotations, the description should explain what 'hydration data' entails (e.g., total intake, time series). It is insufficient for an agent to understand the tool's full behavior and response.

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?

The input schema has 100% description coverage, documenting the single parameter 'date' with format and default. The description adds no extra meaning beyond the schema, so it meets the baseline but does not enhance understanding.

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 clearly states the tool retrieves daily hydration data (water intake). It specifies the resource (hydration data) and the action (get), making the purpose clear. However, it does not differentiate from other 'get_*' siblings, though the name itself is self-explanatory.

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 information is provided about when to use this tool versus others, such as the 'set_hydration' sibling or other data retrieval tools. There are no prerequisites, exclusions, or context on appropriate scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Nicolasvegam/garmin-connect-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server