Skip to main content
Glama
Sign In
oura-mcp-server-enhanced

oura-mcp-server-enhanced

by josuhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_workouts

Retrieve workout sessions including activity type, calories, distance, intensity, and duration for a specified date range.

Instructions

Get workout sessions with activity type, calories burned, distance, intensity, and duration.

Args:
    start_date: Start date in YYYY-MM-DD format. Defaults to yesterday.
    end_date: End date in YYYY-MM-DD format. Defaults to today.

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_workouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
start_dateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided. The description does not disclose any behavioral traits beyond the obvious read operation. No mention of authentication, rate limits, data freshness, or potential side effects.

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 one sentence for the main purpose and a parameter section. Every sentence adds value, no fluff.

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?

Given the existence of an output schema, the description covers the basics. However, it lacks information about data scope (e.g., user-specific), pagination, or filtering capabilities, which would be helpful for a complete picture.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description adds meaning by specifying date format (YYYY-MM-DD) and defaults (yesterday/today), which are not inferable from the schema alone.

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 tool retrieves workout sessions and lists key fields (activity type, calories, distance, intensity, duration). However, it does not differentiate from the sibling tool 'get_sessions', which likely overlaps.

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?

No guidance on when to use this tool versus alternatives like 'get_sessions' or 'get_daily_activity'. The parameter defaults are provided but without context on typical use cases.

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

Deploy Server

Other Tools