Oura MCP Server

Overview Schema Source Related Servers Discussions Admin

get_ring_battery_level

Check the Oura ring’s battery percentage and charging state to know if a recharge is needed. Return the latest reading by default, or request readings over a time window.

Instructions

Get ring battery level (%) and charging state. Returns the latest reading by default; set latest to false for readings over a window.

Input Schema

TableJSON Schema

Name	Required	Description
`latest`	No	Return only the most recent reading.
`next_token`	No	Continue a truncated result: pass the next_token from the previous response along with the same dates.
`end_datetime`	No	End of the window, ISO 8601 datetime. Defaults to now.
`start_datetime`	No	Start of the window, ISO 8601 datetime such as '2026-01-15T00:00:00-08:00'. Defaults to 24 hours before end_datetime.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 26, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the burden of behavioral disclosure. It does add useful behavior beyond the schema by mentioning charging state and the default-vs-window behavior, but it omits details like pagination behavior and time-window defaults, which are only covered by the 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?

Two concise sentences with no filler. The core purpose is front-loaded and the parameter guidance is compact and actionable.

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?

The description plus the fully documented schema and output schema provide enough information for an agent to call this tool correctly. Minor gaps such as pagination and date defaults are already covered by parameter descriptions, so nothing critical is missing.

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 100%, so the schema already documents all four parameters. The description adds context about the latest flag's effect, but does not materially enhance the meaning of the other parameters beyond what the schema provides.

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 identifies the resource (ring battery level) and the specific data returned (percentage and charging state). It is distinct from all sibling tools, which target different health metrics or configuration data.

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?

The description explains the default behavior (latest reading) and how to change it (set latest to false for a window), giving clear operational guidance. It does not explicitly contrast with sibling tools, but the resource is unique enough that no alternative is needed.

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