P.R.O. Apple Health MCP

Daily health metrics

get_daily_metrics

Read-onlyIdempotent

Read daily Apple Health metrics synced to P.R.O. for a bounded recent period. The latest day may be partial; missing days were not synced. Sleep belongs to the night ending on that date. water_ml appears only on days with water logged in Apple Health or in P.R.O. fields_absent identifies untracked fields; restricted identifies fields withheld by sharing settings.

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": "get_daily_metrics"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	How many recent days to return (max 90). Default 14.
`include_hypnogram`	No	Also return sleep_hypnogram per night: consecutive stage runs from sleep_start, e.g. 'c35 d22 r18 a3' (a awake, c light/core, d deep, r REM, u asleep without stage; number = minutes). Off by default — only ask for it when the timeline of a night matters.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.9/5.0

Behavior5/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive call in a closed world, so the description focuses on richer behavioral semantics: partial latest day, unsynced missing days, sleep attributed to the night ending on the date, conditional water_ml presence, fields_absent for untracked fields, and restricted for withheld fields. These details materially improve correct interpretation of the returned data beyond what annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, leading with what is read and for what period. Each subsequent sentence adds a specific data caveat or field meaning rather than repeating structured fields.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only tool with full schema coverage and no output schema, the description supplies the key return-data caveats an agent needs: partial latest day, missing days, sleep attribution, conditional water_ml, and field omission signals. Nothing essential to correct invocation or interpretation appears to be missing.

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 description coverage is 100%, so both parameters are already well documented in the input schema, including the include_hypnogram encoding details. The description does not add parameter-level meaning beyond the schema; the baseline of 3 is appropriate.

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 states a specific verb and resource: read daily Apple Health metrics synced to P.R.O. over a bounded recent period. It is clear what the tool returns and what time scope applies, though it does not explicitly differentiate itself from siblings such as fetch_health_data or get_week_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 gives no explicit when-to-use guidance, no when-not-to-use guidance, and does not name alternatives like fetch_health_data or get_week_summary. Usage is only implied by the phrase 'daily Apple Health metrics ... for a bounded recent period.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All P.R.O. Apple Health MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?