ouraring-mcp

get_daily

Read-only

Retrieve daily Oura summaries for sleep, readiness, activity, stress, SpO2, resilience, or cardiovascular age by date range to answer questions like how you slept this week.

Instructions

Daily summaries for sleep, readiness, activity, stress, spo2, resilience or cardiovascular_age. Best for questions like 'how did I sleep this week?'.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "data_type": "<data_type>"
    },
    "name": "get_daily"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max items (default 50).
`fields`	No	Comma-separated field selector (most routes; not daily_resilience/enhanced_tag/tag).
`end_date`	No
`data_type`	Yes	Which daily summary.
`start_date`	No	Calendar date YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 23, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond the enumeration of data types: nothing about date-range defaults, pagination, whether missing days are returned, or what the response looks like, which matters for an open-world data source.

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?

Two short sentences, front-loaded with the resource, followed by a concrete usage exemplar. Nothing is wasted and nothing is buried.

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

Completeness3/5

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

With five parameters, no output schema, and no annotations about behavior, the description is adequate for invocation but thin on completeness: it never explains the return shape or what the date range does by default, leaving the agent to infer output structure from the data-type names alone.

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 80%, so start_date, end_date, limit, and data_type are already documented in the schema. The description merely restates the same data-type list and adds no format or semantics beyond it; baseline 3 applies.

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?

Names a specific resource ('daily summaries') and enumerates the seven supported data types, which maps precisely onto the data_type enum. An agent can distinguish this from get_collection or list_collections, though it never explicitly contrasts with the close sibling get_recent_summary.

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 line 'Best for questions like how did I sleep this week?' gives an implied usage context, which is more than nothing. However, there is no explicit when-not guidance and no named alternative for nearby cases such as get_recent_summary, so routing between the two is left to inference.

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

Deploy Server