Skip to main content
Glama

Oura Daily Readiness

oura_list_daily_readiness
Read-onlyIdempotent

Retrieve daily Oura readiness summaries and contributing factors to assess recovery and plan training.

Instructions

List Oura readiness summaries and contributors. Requires daily scope. Not medical advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNoOnly return Oura records after this time. Converted to an Oura start_date.
limitNoMaximum number of records returned by this call, kept from the OLDEST end of the window. Oura v2 serves collections oldest-first, has no sort parameter and no page-size parameter, so limit=1 returns the OLDEST record in the window, never the newest. To get the most recent record of this domain, read the resource oura://latest/readiness, which walks the Oura cursor to the end of the window instead of stopping at its oldest block. Narrowing the window with after/before also works. The cap is applied locally after fetching and also stops cursor pagination once it is reached; when it dropped records, truncated is true and has_more is true. If truncated is true, raise limit or set all_pages — do not follow a cursor, because next_token is omitted whenever resuming would skip dropped records.
beforeNoOnly return Oura records before this time. Converted to an Oura end_date.
all_pagesNoWhen true, follow the Oura next_token cursor up to max_pages in this one call. Resume later by passing the returned next_token with the same after/before window.
max_pagesNoMaximum upstream Oura pages to fetch in this call when all_pages is true. A runaway guard, not an Oura page index.
next_tokenNoOpaque Oura v2 cursor from a previous collection response. Pass it back unchanged with the same after/before window to resume. Oura has no integer page index and no page-size parameter; do not invent or increment a page number.
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_moreYesTrue when more records exist beyond this response, either upstream (a resumable next_token) or because the limit cap dropped records (truncated). If truncated is true, raise limit or set all_pages; if next_token is present, pass it back.
truncatedYesTrue when the limit cap dropped records that had already been fetched. Raise limit or set all_pages (or narrow after/before) to see them. next_token is omitted in this case so a resume cannot skip those rows.
next_tokenNoOpaque Oura v2 cursor to resume from. Pass this back as input next_token with the same after/before window. Present only when more records exist upstream AND this call did not locally drop fetched records (truncated is false). When truncated is true, next_token is omitted: raise limit or set all_pages instead of following a cursor, which would skip the dropped records. Never increment a page number.
privacy_modeYes
pages_fetchedYes
Install Server

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds a useful auth prerequisite ('Requires daiily scope') and a medical disclaimer, but does not disclose pagination, sorting, or truncation behavior beyond what parameter docs already state. It does not contradict annotations.

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?

Three short sentences with no filler. The action is front-loaded ('List Oura readiness summaries and contributors'), followed by the scope requirement and disclaimer. Every sentence earns its place.

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?

For a tool with a rich input schema, output schema, and strong annotations, the description is mostly sufficient. It names the resource and required scope, while the schema and parameter docs handle pagination, privacy modes, and return details. The main gap is lack of tool-selection guidance, but that is a usage_guidelines issue, not a completeness issue.

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 89%, well above the 80% threshold, so the baseline is 3. The top-level description adds no parameter detail; the schema itself thoroughly documents after/before, limit, next_token, privacy_mode, and related parameters.

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 uses a specific verb ('List') with a clear resource ('Oura readiness summaries and contributors'), so an agent knows what the tool returns. It does not explicitly distinguish this from sibling list tools like oura_daily_summary or oura_list_daily_activity, but the resource noun is specific enough.

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 only context is a prerequisite ('Requires daily scope') and a disclaimer ('Not medical advice'), with no guidance on when to prefer this tool over alternatives such as oura_daily_summary or oura_list_daily_activity. No exclusions or alternative routing are mentioned.

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

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