Oura MCP Server

Overview Schema Source Related Servers Discussions Admin

get_rest_mode_periods

Retrieve rest mode periods with start and end times and logged episodes by date range. Useful for tracking illness or recovery periods from Oura data.

Instructions

Get rest mode periods (when the user turned on rest mode, typically for illness or recovery), with start and end times and logged episodes.

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

Input Schema

Name	Required	Description
`end_date`	No	Last day to include (inclusive), YYYY-MM-DD. Defaults to today.
`next_token`	No	Continue a truncated result: pass the next_token from the previous response along with the same dates.
`start_date`	No	First day to include, YYYY-MM-DD. Defaults to 6 days before end_date.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. 'Get' implies a read operation, but the description does not state that it is read-only, does not mention authentication requirements, pagination behavior, or rate limits, and offers no detail beyond the returned data.

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?

The description is a single, front-loaded sentence that clearly identifies the tool's purpose and output. It contains no unnecessary repetition or fluff, though some additional usage guidance could have been included without harming conciseness.

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?

The tool has a simple schema with fully documented optional parameters and an output schema, so the description is minimally sufficient for invocation. However, the lack of annotations and absence of any behavioral context (auth, read-only confirmation, pagination) leaves the description slightly incomplete for a fully informed agent.

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 the input schema fully documents start_date, end_date, and next_token. The description adds no parameter-specific detail beyond the schema, so the baseline score 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 ('Get rest mode periods') and indicates what is returned (start/end times and logged episodes). It does not explicitly differentiate from siblings like get_sleep_periods, but the resource is distinct enough for an agent to understand the tool's purpose.

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 mentions rest mode is typically used for illness or recovery, but it provides no guidance on when to choose this tool over siblings like get_sleep_periods or get_sessions. There is no explicit context for selection or exclusion of alternatives.

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