Skip to main content
Glama

Oura Daily SpO2

oura_list_daily_spo2
Read-onlyIdempotent

Retrieve daily SpO2 averages recorded during sleep from Oura Ring. View blood oxygen levels for each sleep period.

Instructions

List daily Oura SpO2 averages recorded during sleep when available. Requires spo2 scope. 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
Behavior3/5

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

Annotations already declare read-only and non-destructive behavior. The description adds limited behavioral context by stating data is 'when available' and includes a disclaimer. This slightly enhances transparency but the main burden is carried by 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 covering purpose, requirement, and disclaimer. It is front-loaded and efficient, though it could be slightly expanded without losing conciseness.

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 the existence of an output schema and many sibling tools, the description lacks contextual completeness. It does not explain what SpO2 is, typical use cases, or how it relates to other daily data tools. More context would help an agent select and invoke the tool appropriately.

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 (89%), so the description is not required to add much. It does not provide additional meaning beyond the schema except for noting the required scope, which is about authorization rather than parameters.

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?

The description clearly states the tool lists daily Oura SpO2 averages recorded during sleep, with a specific verb and resource. It distinguishes itself from siblings like oura_list_daily_sleep by focusing on SpO2 data.

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 only mentions the required 'spo2 scope' but provides no guidance on when to use this tool versus alternatives or when not to use it. No comparison with sibling tools is made.

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