Oura MCP Server

Overview Schema Source Related Servers Discussions Admin

get_heart_rate

Retrieve heart rate samples (bpm) recorded every 5 minutes, tagged by source (awake, rest, sleep, workout, session, live). Defaults to last 24 hours; supports aggregation and latest-sample options.

Instructions

Get heart rate samples (bpm) at roughly 5 minute intervals, each tagged with its source: awake, rest, sleep, workout, session or live. Defaults to the last 24 hours.

Input Schema

TableJSON Schema

Name	Required	Description
`latest`	No	Return only the most recent sample.
`aggregate`	No	Summarize samples into hourly or daily min/avg/max buckets (UTC). Recommended for windows longer than a day; raw data is 288 samples a day.
`next_token`	No	Continue a truncated result: pass the next_token from the previous response along with the same dates.
`end_datetime`	No	End of the window, ISO 8601 datetime. Defaults to now.
`start_datetime`	No	Start of the window, ISO 8601 datetime such as '2026-01-15T00:00:00-08:00'. Defaults to 24 hours before end_datetime.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the sampling interval and default window, but does not mention pagination via next_token, aggregation recommendations, error behavior, or any edge cases. The schema covers some of this, but the description itself is thin on behavioral disclosure.

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?

A single, front-loaded sentence with no fluff. It immediately states the purpose, data details, and default behavior, making it efficient and easy to parse.

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 the existence of an output schema and complete parameter descriptions, the description is adequate for a simple read operation. However, it lacks usage guidance and behavioral context that could help an agent decide when to use this tool or handle large result sets. It is not incomplete but not comprehensive either.

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 coverage is 100% with descriptive parameter definitions. The tool description adds minimal value beyond schema—it mentions the default window and data characteristics but does not clarify parameter usage beyond what is already in the schema. Baseline 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 clearly states the tool retrieves heart rate samples in bpm at 5-minute intervals, tagged with source types, and mentions the default window. It is specific and distinct from other health-related siblings, though it does not explicitly contrast with alternatives.

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?

No guidance is provided on when to use this tool versus alternatives, nor are there exclusions or context about when to prefer aggregate vs raw data. The description only mentions defaults, which is not usage direction.

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