Skip to main content
Glama

get_daily_health_snapshot

Aggregate complete daily health metrics including heart rate, stress, body battery, sleep, HRV, respiration, SpO2, steps, floors, and intensity minutes in a single request. Defaults to today's data, or yesterday if today's is unavailable.

Instructions

Get complete daily health snapshot in a single call: summary, heart rate, stress, body battery, sleep, HRV, respiration, SpO2, steps, floors, intensity minutes. Calls ~11 endpoints in parallel. Use yesterday if today has no data yet

Input Schema

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

Implementation Reference

  • Core handler that executes the tool logic: fetches daily summary, heart rate, stress, body battery, sleep, HRV, respiration, SpO2, steps, floors, and intensity minutes in parallel, returning a combined snapshot object.
    async getDailyHealthSnapshot(date?: string): Promise<Record<string, unknown>> {
      const resolvedDate = date ?? todayString();
    
      const [summary, heartRate, stress, bodyBattery, sleep, hrv, respiration, spo2, steps, floors, intensityMinutes] =
        await Promise.all([
          this.getDailySummary(resolvedDate).catch(() => null),
          this.getHeartRate(resolvedDate).catch(() => null),
          this.getStress(resolvedDate).catch(() => null),
          this.getBodyBattery(resolvedDate, resolvedDate).catch(() => null),
          this.getSleepData(resolvedDate).catch(() => null),
          this.getHRV(resolvedDate).catch(() => null),
          this.getRespiration(resolvedDate).catch(() => null),
          this.getSpO2(resolvedDate).catch(() => null),
          this.getStepsChart(resolvedDate).catch(() => null),
          this.getFloors(resolvedDate).catch(() => null),
          this.getIntensityMinutes(resolvedDate).catch(() => null),
        ]);
    
      return {
        date: resolvedDate,
        summary,
        heartRate,
        stress,
        bodyBattery,
        sleep,
        hrv,
        respiration,
        spo2,
        steps,
        floors,
        intensityMinutes,
      };
    }
  • Registers the 'get_daily_health_snapshot' tool on the MCP server with its description, input schema, and callback that delegates to the client.
    export function registerSnapshotTools(server: McpServer, client: GarminClient): void {
      server.registerTool(
        'get_daily_health_snapshot',
        {
          description:
            'Get complete daily health snapshot in a single call: summary, heart rate, stress, body battery, sleep, HRV, respiration, SpO2, steps, floors, intensity minutes. Calls ~11 endpoints in parallel. Use yesterday if today has no data yet',
          inputSchema: dateParamSchema.shape,
        },
        async ({ date }) => {
          const data = await client.getDailyHealthSnapshot(date);
          return {
            content: [{ type: 'text' as const, text: JSON.stringify(data, null, 2) }],
          };
        },
      );
    }
  • Zod schema for the optional 'date' parameter used as input to the tool.
    export const dateParamSchema = z.object({
      date: dateString
        .optional()
        .describe('Date in YYYY-MM-DD format. Defaults to today if not provided'),
    });
  • src/index.ts:47-47 (registration)
    Top-level registration call that wires the snapshot tools to the server and client.
    registerSnapshotTools(server, client);
  • Re-exports registerSnapshotTools from the snapshot.tools module.
    export { registerSnapshotTools } from './snapshot.tools';
    export { registerTrainingTools } from './training.tools';
    export { registerWellnessTools } from './wellness.tools';
    export { registerChallengeTools } from './challenges.tools';
Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions parallel endpoint calls and the fallback date logic, which adds useful context. However, it lacks details on authentication, rate limits, or potential delays from parallel execution.

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

Conciseness5/5

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

The description is two sentences, front-loaded with the core purpose, and efficiently conveys the tool's scope and behavioral note without redundancy.

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

Completeness4/5

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

Given the absence of an output schema, the description lists the returned metrics, which is helpful. However, it omits the structure of the response (e.g., JSON format) and doesn't detail how errors are handled, but overall it is sufficient for the tool's simplicity.

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?

The schema already covers the date parameter format and default, but the description adds value by clarifying the fallback behavior ('Use yesterday if today has no data yet'), enhancing understanding of the date logic.

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 clearly states it retrieves a complete daily health snapshot, listing specific metrics (heart rate, stress, sleep, etc.). It distinguishes itself from sibling tools by aggregating ~11 endpoints in a single call, as opposed to individual metric tools like get_heart_rate or get_sleep_data.

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 provides context by noting it aggregates multiple endpoints and suggests using yesterday's data if today's is unavailable. However, it could more explicitly state when to use this composite tool versus individual ones, e.g., for a comprehensive overview vs. a single metric.

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