Skip to main content
Glama

Oura Sleep Periods

oura_list_sleep
Read-onlyIdempotent

Retrieve detailed Oura sleep period records including sleep stages and timing. Filter by date range to analyze sleep patterns.

Instructions

List detailed Oura sleep period records, including sleep stages and timing where available. Requires sleep scope. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOnly return Oura records after this time. Converted to an Oura start_date.
beforeNoOnly return Oura records before this time. Converted to an Oura end_date.
pageNoOura page number.
limitNoLocal page-size hint used for pagination safety.
all_pagesNoFetch multiple pages up to max_pages.
max_pagesNoMaximum pages to fetch when all_pages is true.
privacy_modeNoOptional per-call privacy override. Defaults to OURA_PRIVACY_MODE or structured. raw returns upstream Oura JSON. summary minimizes sensitive health and profile details.
response_formatNomarkdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
endpointYes
privacy_modeYes
countYes
recordsYes
next_pageNo
has_moreYes
pages_fetchedYes
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the behavioral constraint 'Requires sleep scope', which is useful context beyond annotations.

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 very concise with three short sentences, front-loaded with the main action. No wasted words, but could be slightly expanded to improve clarity.

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?

Given the presence of an output schema and comprehensive annotations, the description covers the key context (scope requirement, disclaimer) and is largely complete. However, it does not differentiate from sibling tools.

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 high (88%), so the baseline is 3. The description does not add significant additional meaning beyond the parameter descriptions already in the schema.

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 verb 'List' and the resource 'detailed Oura sleep period records', including sleep stages and timing. However, it does not explicitly distinguish itself from the sibling tool 'oura_list_daily_sleep', which likely returns daily summaries rather than detailed period records.

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 mentions 'Requires sleep scope' as a prerequisite and includes a 'Not medical advice' disclaimer, but does not provide guidance on when to use this tool versus alternatives like 'oura_list_daily_sleep' or other Oura list tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/oura-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server