Skip to main content
Glama

Oura Workouts

oura_list_workouts
Read-onlyIdempotent

List Oura workout summaries with pagination and date filtering.

Instructions

List Oura workout summaries. Requires workout scope.

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?

The annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds the behavioral trait that 'Requires workout scope', which is important context beyond the annotations. No contradictions detected.

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?

The description is extremely concise with only two sentences. Every word serves a purpose, and no extraneous information is included. This is an excellent example of brevity.

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?

Given the tool's complexity (simple list operation with well-documented parameters and an output schema), the description is sufficiently complete. It covers the essential purpose and a key prerequisite. While it could mention pagination hints explicitly, the parameters already handle that.

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 underlying schema already documents parameters well. The tool description does not add additional meaning to the parameters beyond what is in the schema. A score of 3 is appropriate as the description does not compensate for any gaps.

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 clearly states the verb 'List' and the resource 'Oura workout summaries', making the tool's purpose evident. It also includes a prerequisite ('Requires workout scope'). However, it does not differentiate this tool from sibling list tools for other Oura data types, which slightly reduces clarity.

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 description mentions the required scope, providing basic guidance on when the tool can be used. However, it does not discuss alternatives or when to prefer this tool over other Oura list tools (e.g., oura_list_daily_activity). No explicit 'when to use' or 'when not to use' instructions are given.

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