Skip to main content
Glama
davidmosiah

Apple Health MCP

by davidmosiah
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Clear Apple Health Incremental Import Cache

apple_health_clear_incremental_cache
DestructiveIdempotent

Clear the incremental cache to force a full re-parse of Apple Health export data on the next list records call. Use when you need to re-read all records without modifying the export file.

Instructions

Manually clear the incremental import cache at ~/.apple-health-mcp/incremental-cache.json. The cache tracks the latest parsed timestamp per HealthKit category so subsequent apple_health_list_records calls (with incremental_cache: true) skip already-seen records. Use this when you want to force a full re-parse without changing the export file. The cache also auto-invalidates when the export file mtime changes. Gated by explicit_user_intent: true (requires explicit user intent to wipe local cache).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
response_formatNomarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4/5.0
Behavior5/5

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

Clearly describes destructive action (wipes local cache) and gated by explicit_user_intent. This adds context beyond annotations like destructiveHint and idempotentHint. No contradictions.

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 paragraph with front-loaded purpose, followed by context. Four sentences with no wasted words, though slightly longer than minimal.

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?

Covers cache purpose, file path, auto-invalidation, and user intent requirement. No output schema, but behavior is simple and described well. Lacks explanation of what happens after clearing.

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

Parameters1/5

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

Schema coverage is 0%, but description does not mention the single parameter 'response_format' or its enum values (markdown/json). Agent gets no guidance on output format beyond schema.

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?

Clear verb 'clear' with specific resource 'incremental import cache' and file path. Explanation of cache purpose and when to use distinguishes from siblings like listing or importing records.

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?

Explicitly states use case: 'force a full re-parse without changing the export file.' Mentions auto-invalidation hinting when not needed, but no explicit alternative tool named.

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