Query an Apple Health export with an LLM over MCP, with a clinical semantic layer that stops the model misreading the data. Optionally correlates CPAP therapy data from OSCAR.
Three tools with clear semantic purpose (health data querying). All have descriptions and input schemas. However, parameter descriptions are sparse or missing entirely. health_query lacks descriptions for 'query' and 'limit' parameters. health_report lacks descriptions for 'startDate', 'endDate', and 'metrics' parameters. No output schemas documented. Error handling is minimal, no guidance on recovery or retryability. Tool names are verb-noun but generic (health_query could be confused with health_schema). No tool annotations (readOnlyHint, etc.) despite all being read-only. Descriptions are adequate (100-200 chars) but could be more prescriptive about when to call each tool vs. the others.
Run a read-only DuckDB SQL query against the health tables. Call health_schema first so you know the columns and the correct aggregate function for each metric.
Generate a structured report of health metrics over a time period, with automatic aggregation and unit normalization.
List every available health table and return the curated semantic layer: what each metric measures, which aggregate function is valid for it, and the known traps in the data. Call this before writing any query.
health_query and health_report lack parameter descriptions. 'query' parameter has no description; 'limit', 'startDate', 'endDate', 'metrics' are undescribed. LLMs cannot infer parameter meaning from names alone.
No output schemas documented for any tool. LLMs cannot plan downstream operations or extract required fields without knowing response structure.
No tool annotations despite all tools being read-only. Missing readOnlyHint would help agents understand safety and retry semantics.
health_query accepts 'limit' (1 - 5000) but no validation or error guidance if LLM passes invalid values. No constraint description in parameter.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Error handling is minimal. No recovery guidance. If health_schema returns 'No health data tables found', the response includes a suggestion, but health_query and health_report lack similar error context.