Skip to main content
Glama

Oura Daily Sleep

oura_list_daily_sleep
Read-onlyIdempotent

Retrieve daily sleep score summaries from your Oura Ring to review sleep quality and duration.

Instructions

List daily Oura sleep score summaries. Requires daily or sleep data access granted by the user. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOura page number.
afterNoOnly return Oura records after this time. Converted to an Oura start_date.
limitNoLocal page-size hint used for pagination safety.
beforeNoOnly return Oura records before this time. Converted to an Oura end_date.
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
explicit_user_intentNoRequired true when privacy_mode=raw (agent escalation of redaction).

Output Schema

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

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

Annotations already declare readOnly, idempotent, not destructive. Description adds only access requirement and legal disclaimer, no behavioral context like pagination, privacy modes, or response handling beyond schema.

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?

Very concise: one short sentence stating purpose, followed by two necessary caveats. No wasted words, front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 9 parameters, pagination, privacy modes, and many sibling tools, the description is too sparse. Missing context on results, pagination behavior, and how it differs from similar list 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 coverage is 89%, so parameter descriptions in schema carry most meaning. Tool description does not add parameter semantics beyond what schema provides.

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 verb 'List' and resource 'daily Oura sleep score summaries'. Clear purpose but does not explicitly differentiate from sibling tools like oura_list_sleep or oura_list_daily_activity.

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?

Only mentions data access requirement and legal disclaimer. No guidance on when to use this tool versus alternatives or when not to use it.

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