P.R.O. Apple Health MCP

Workouts

get_workouts

Read-onlyIdempotent

Read recorded workout headers for a period and optional sport. Includes a workouts card. Headers do not contain detailed GPS tracks or health samples.

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_workouts"
  }
}

Input Schema

Name	Required	Description
`days`	No	How many recent days to cover (max 3650 — the whole synced history). Default 30. Ignored when since is given.
`since`	No	Start of an exact period, YYYY-MM-DD (inclusive). Use for questions like 'my runs in 2024' or 'last March'.
`sport`	No	Optional sport/workout type filter, e.g. running, cycling, swimming.
`until`	No	End of the period, YYYY-MM-DD (inclusive). Defaults to today.
`include_details`	No	Also return, for recent workouts, hr_series (average bpm per hr_bucket_s seconds from the start, '-' = no reading), splits_pace (minutes per km as decimals, one per completed km: '6.34' = 6 min 20 s), splits_hr and elevation_gain_m. Off by default.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds two useful pieces beyond that: results are headers only (no GPS tracks or health samples) and it 'includes a workouts card' — an undocumented UI side effect worth knowing. That is real added context but not rich behavioral detail (no pagination, no result shape).

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?

Three short sentences, front-loaded with the core action, then the side effect, then the limitation. No filler or repetition.

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?

With full annotations, fully documented parameters and no output schema, the description covers the essentials and usefully warns that detailed samples and tracks are absent. A brief mention of the return shape (what a 'workout header' contains) would close the remaining gap.

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 every parameter (days, since, sport, until, include_details) is already fully documented in the schema, including precedence rules like 'ignored when since is given'. The description only echoes period and sport and hints that detailed tracks require more than headers; it adds essentially nothing the schema does not already say.

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?

States a specific verb and resource ('Read recorded workout headers') plus the scoping dimensions (period, optional sport), which is more precise than the bare title 'Workouts'. It does not name a sibling tool, so the boundary with fetch_health_data or get_daily_metrics is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage ('for a period and optional sport') and signals what the tool will not return (GPS tracks, health samples), which helps route away from it. However, it never states when to pick this over fetch_health_data or get_daily_metrics, and gives no explicit exclusions or prerequisites.

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?