Skip to main content
Glama
echocharlie

Oura MCP Server

by echocharlie

oura_get_sleep_time

Read-only

Retrieve Oura's optimal bedtime window and recommendation to see if you are going to bed at the right time based on your circadian data.

Instructions

Oura's own bedtime guidance: the optimal bedtime window and what it recommends.

Use to answer "am I going to bed at the right time?" — distinct from oura_get_daily_summary's bedtime, which reports when you ACTUALLY slept. This is what Oura thinks you SHOULD do, derived from your circadian/temperature data.

CSV columns: date, optimal_bedtime_start, optimal_bedtime_end (local HH:MM; blank when Oura couldn't compute a window), recommendation, status

recommendation is one of: follow_optimal_bedtime — you're aligned; keep the current window earlier_bedtime — go to bed earlier later_bedtime — go to bed later earlier_wake_up_time / later_wake_up_time — adjust the wake side instead

status is one of: optimal_found — a concrete window was computed (times populated) only_recommended_found — Oura has a direction but NOT enough data for a window, so the time columns are blank. This is normal, not an error. not_enough_nights / no_data — insufficient history in the range.

Note: Oura returns these times as raw second-offsets from local midnight; this tool decodes them to HH:MM. A run of identical earlier_bedtime rows means Oura has been persistently flagging late sleep timing — worth reading as a trend, not a single day.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateNoISO end date (YYYY-MM-DD), inclusive. Defaults to today.
start_dateNoISO start date (YYYY-MM-DD). Defaults to a 30-day window ending at end_date.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Annotations already indicate readOnlyHint=true. Description adds extensive behavioral context: explains CSV columns, enumerations for recommendation and status, notes blank times for status 'only_recommended_found', and advises reading trends over single days. No contradiction.

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?

Well-structured with purpose upfront, followed by columns and enumerations in bullet-like format. Slightly lengthy but every part adds value; no fluff.

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?

Given 2 optional parameters and presence of output schema, description independently and thoroughly explains the output format (CSV columns, possible values) and edge cases (blank times, trend reading). Complete for a data-retrieval tool.

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%, so baseline is 3. Description does not add meaning beyond schema for start_date and end_date; it focuses on output interpretation. No additional parameter context given.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states 'Oura's own bedtime guidance: the optimal bedtime window and what it recommends.' It explicitly distinguishes from sibling oura_get_daily_summary's `bedtime`, which reports actual sleep time, thus differentiating resource and scope.

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

Usage Guidelines5/5

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

Explicitly says 'Use to answer "am I going to bed at the right time?"' and contrasts with oura_get_daily_summary, providing a clear alternative and when-not-to-use.

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/echocharlie/oura-mcp-server'

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