Retrieve Oura Ring heart rate time series data in BPM with timestamps and source info using start and end datetime parameters.
Get heart rate time series data. Returns heart rate readings (BPM) with timestamps and source information. Uses datetime range parameters instead of date range.
| Name | Required | Description | Default |
|---|---|---|---|
| next_token | No | ||
| end_datetime | No | ||
| start_datetime | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It usefully discloses the return content (BPM readings with timestamps and source), but omits pagination behavior implied by next_token, as well as any auth or rate-limit context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with purpose, no filler. The third sentence about datetime parameters is useful but could be integrated more tightly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with no output schema and no annotations, the description covers purpose, return shape, and parameter style. However, missing datetime format and pagination semantics leaves gaps that an agent must infer.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%. The description loosely covers start_datetime and end_datetime by noting they are datetime ranges rather than date ranges, but gives no format details, and next_token is entirely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Get heart rate time series data') and clarifies it returns raw readings rather than daily summaries. Distinguishes from date-range siblings by noting datetime range parameters, but does not explicitly name any sibling tool.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No when-to-use guidance or alternatives are given. The datetime-vs-date note is a parameter format hint, not usage guidance, and there are no exclusions or prerequisites mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.