Skip to main content
Glama
daveremy

Apple Health MCP

by daveremy
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Workouts

apple_health_workouts

Retrieve Apple Health workout session data for a specific date to analyze fitness activities and performance metrics from local iCloud storage.

Instructions

Get workout sessions for a date

Input Schema

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

Implementation Reference

  • src/mcp.ts:248-256 (handler)
    Registration and handler implementation for the apple_health_workouts tool.
    server.registerTool("apple_health_workouts", {
  title: "Workouts",
  description: "Get workout sessions for a date",
  inputSchema: z.object({ date: optDate }),
}, async ({ date }) => {
  const d = date ?? today();
  const workouts = parseWorkouts(d);
  return text({ date: d, count: workouts.length, workouts });
});

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. 'Get' implies read-only safety, but description omits what data structure returns (list of workouts, duration, types, calories), behavior when no workouts exist, or whether this includes all activity types. No output schema compounds this gap.

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?

Extremely concise (6 words) and front-loaded with verb-first structure. No redundant phrases. However, brevity arguably underserves tool's behavioral complexity given lack of annotations and output schema.

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?

Acceptable for a single-parameter tool with 100% schema coverage, but gaps remain. Missing: return value description (critical without output schema), explicit sibling differentiation, and confirmation of read-only behavior. Minimum viable but not exemplary.

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 coverage is 100% (date parameter fully documented with format and default). Description references 'a date' acknowledging the parameter exists, but adds no semantic detail beyond schema's 'YYYY-MM-DD, defaults to today'. Baseline score appropriate given schema completeness.

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?

Clear verb 'Get' and resource 'workout sessions'. Scope 'for a date' implies filtering by specific date. Implicitly distinguishes from siblings by focusing on individual sessions vs aggregates (daily/trends), though explicit differentiation would strengthen this.

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 guidance on when to use this versus apple_health_daily or apple_health_trends. Agent must infer that 'workouts' retrieves individual exercise sessions while siblings handle aggregated metrics. No mention of prerequisites or date range limitations.

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