Skip to main content
Glama

Daily Summary

apple_health_daily

Retrieve daily Apple Health metrics including steps, heart rate, sleep stages, workouts, and body composition from local iCloud storage for health analysis.

Instructions

Get Apple Health daily summary: steps, energy, HR, HRV, sleep stages, body comp, workouts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, defaults to today

Implementation Reference

  • Tool registration and handler implementation for apple_health_daily in src/mcp.ts.
    server.registerTool("apple_health_daily", {
      title: "Daily Summary",
      description: "Get Apple Health daily summary: steps, energy, HR, HRV, sleep stages, body comp, workouts",
      inputSchema: z.object({ date: optDate }),
    }, async ({ date }) => {
      const d = date ?? today();
      const metrics = parseMetrics(d);
      if (!metrics) return text({ error: `No health data found for ${d}`, path: METRICS_DIR });
      const workouts = parseWorkouts(d);
      return text(formatDailySummary(d, metrics, workouts));
    });
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. It enumerates the data categories returned, which helps understand scope. However, it lacks behavioral details such as error handling for future dates, privacy/auth requirements, data availability when Health permissions are denied, or whether values are summed/averaged.

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?

Single efficient sentence front-loaded with the action. The colon-separated list of metrics is compact and readable. No extraneous text, though slightly dense.

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?

Without output schema, the description adequately compensates by listing the seven metric categories returned. However, for a health data tool with no annotations, it should clarify behavior regarding missing data (null values vs zeros) and permission requirements to be fully complete.

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 has 100% coverage (date field fully documented with format and default), establishing baseline 3. Description does not add semantic context about the date parameter (e.g., timezone handling, how 'today' is determined), but none is required given complete schema documentation.

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?

Uses specific verb 'Get' and resource 'Apple Health daily summary'. Lists specific metric categories (steps, energy, HR, HRV, sleep stages, body comp, workouts) clarifying scope. However, it does not explicitly differentiate from sibling 'apple_health_workouts' despite mentioning workouts in its data list, nor contrast with 'apple_health_trends'.

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?

Provides no guidance on when to use this tool versus the sibling 'trends' or 'workouts' tools. The inclusion of 'workouts' in the daily summary list without qualification creates potential ambiguity about whether this returns summary workout statistics or detailed records.

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/daveremy/apple-health-mcp'

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