Retrieve daily sleep scores and contributor breakdowns, including deep sleep, REM, efficiency, latency, restfulness, timing, and total sleep for specified dates.
Get daily sleep scores and contributor breakdown. Returns sleep score with contributors like deep sleep, efficiency, latency, REM sleep, restfulness, timing, and total sleep.
| Name | Required | Description | Default |
|---|---|---|---|
| end_date | No | ||
| next_token | No | ||
| start_date | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries full behavioral burden. It mentions return contributors but does not disclose pagination (implied by next_token), date range requirements, or whether results are limited to a single day. This leaves significant behavioral gaps for a data retrieval tool.
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?
The description is concise, two sentences, and front-loads the purpose before listing contributors. No superfluous text. However, it could better structure the return details or scoping constraints.
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?
The tool has three parameters with no schema descriptions, no annotations, no output schema, and a complex sibling ecosystem. The description does not compensate for missing parameter semantics or behavioral traits like pagination and date filtering. It is incomplete for an agent to call correctly.
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%, meaning none of the three parameters (start_date, end_date, next_token) are documented in the schema. The description adds no meaning for these parameters, providing no syntax, format, or purpose information. This is a critical deficiency.
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?
The description clearly states a specific verb and resource: 'Get daily sleep scores and contributor breakdown.' It distinguishes the resource (daily sleep scores) from siblings like get_sleep (raw sleep data) or get_sleep_time. However, it does not explicitly name an alternative or clarify how it differs from get_sleep_by_id and get_daily_sleep_by_id, so it falls short of a 5.
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 guidance is provided on when to use this tool versus alternatives such as get_sleep, get_sleep_by_id, or get_daily_sleep_by_id. The description implies usage (retrieve daily sleep scores) but offers no conditions, exclusions, or routing hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.