ouraring-mcp

get_recent_summary

Read-only

Retrieve a combined summary of recent Oura Ring sleep, readiness, activity, stress, and SpO2 data for a chosen number of days to answer questions such as How was my week?

Instructions

One-call overview of the last N days (sleep + readiness + activity + stress + spo2 daily summaries) for natural-language summaries like 'how was my week?'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_recent_summary"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No	Recent calendar days (default 7, max 90).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only and open-world traits, so the description only needs to add what they don't. It does: the key behavior is batching five domain summaries into a single call, and it enumerates which domains come back. It says nothing about response shape or payload size, which matters for the 90-day max, but the core behavior is disclosed.

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?

A single front-loaded clause covers what it does, which domains it includes, and a usage example. Every element earns its place, and nothing is padded.

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?

With one optional parameter, no output schema, and annotations covering safety, the remaining burden is telling the agent what comes back. The domain list does that adequately; a brief note on return granularity (daily-per-domain) would close the last gap.

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%, and the schema already documents the default of 7 and the max of 90. The description's 'last N days' only restates the parameter, so the 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?

States a specific verb and resource: a one-call aggregated overview over the last N days spanning five named domains (sleep, readiness, activity, stress, spo2). That is clearly distinct from get_daily, though the description never names the sibling to make the contrast explicit.

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

Usage Guidelines4/5

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

Gives a concrete triggering scenario ('how was my week?') that tells the agent when to reach for this aggregated tool. It stops short of an explicit exclusion such as 'use get_daily for a single day', so the boundary is inferred rather than stated.

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

Deploy Server