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

oura-mcp-server-enhanced

by josuhr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_sleep_time

Retrieve recommended and actual sleep timing windows for any date range.

Instructions

Get recommended and actual sleep timing windows.

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

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/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only gives parameter format and defaults. It does not explain what 'recommended' means, whether data is read-only, or any 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with a clear summary line followed by parameter documentation. No extra words, but the summary could be slightly more descriptive.

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

Completeness2/5

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

Despite having an output schema, the description does not describe the return structure beyond 'sleep timing windows.' This is incomplete for a tool expected to return complex data.

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's docstring explains both parameters with format and defaults, adding meaning beyond the schema's property definitions.

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 it retrieves recommended and actual sleep timing windows. It distinguishes from siblings by focus on timing windows, though it doesn't explicitly contrast with similar sleep tools.

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 is given on when to use this tool versus alternatives like get_daily_sleep or get_sleep_data. The description only explains function, not context or exclusions.

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