Skip to main content
Glama
Sign In
Apple Health MCP

Apple Health MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Apple Health Wellness Context

apple_health_wellness_context
Read-onlyIdempotent

Normalize local Apple Health sleep, workout, and activity data into a shared wellness context for recommendation engines, with date, notes, soreness, and injury flags.

Instructions

Normalize local Apple Health export sleep, workout and activity data into the shared wellness_context shape for recommendation engines.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "apple_health_wellness_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD local date. Defaults to today in the configured timezone.
notesNo
sorenessNo
timezoneNoIANA timezone, e.g. America/Fortaleza. Defaults to APPLE_HEALTH_TIMEZONE or UTC.
injury_flagsNo
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds context about data transformation into a specific shape, which is valuable but does not disclose any additional behavioral traits such as side effects or prerequisites. With annotations covering the core safety profile, this is adequate.

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 a single sentence that concisely conveys the core purpose without extraneous information. It is front-loaded with the verb and resource. However, it could be more structured by adding parameter hints or usage context.

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?

Given 6 optional parameters, no output schema, and a moderate-complexity tool, the description is minimally adequate. It explains the high-level purpose but lacks details on the output shape, normalization logic, and parameter roles. For an agent to use it effectively, more context is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33% (only date and timezone have descriptions). The tool description does not mention any parameters or explain their semantics, leaving the agent to rely only on the schema. Since coverage is low, the description should compensate but does not.

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 action (Normalize) and the specific resource (local Apple Health export sleep, workout and activity data) and the outcome (shared wellness_context shape for recommendation engines). It distinguishes itself from sibling tools by mentioning the specific output format, but it does not explicitly differentiate from similar transformation tools like apple_health_daily_summary.

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?

The description does not provide any guidance on when to use this tool versus alternatives, nor does it specify prerequisites or exclude conditions. An agent has no context to decide between this and apple_health_daily_summary or other sibling tools.

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