Retrieve complete sleep details for a specific date to analyze sleep stages, duration, and quality. Provides full dataset for in-depth sleep analysis.
Get full sleep data with all details
Note: This returns detailed sleep data (~50KB). For a compact summary, use get_sleep_summary().
Args: date: Date in YYYY-MM-DD format
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It adds one useful trait—the response is detailed and roughly 50KB—which is relevant for an agent deciding whether to call it. However, it does not mention authentication, rate limits, or other behavioral constraints, though as a read-only getter the risk is modest.
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 compact and well-structured with the purpose first, followed by the critical payload-size note and then the argument format. Every sentence earns its place, and there is no redundant or vague wording.
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?
Given the single required parameter, an output schema, the explicit date format, and the pointer to a lighter-weight alternative, the description provides enough context for correct invocation. The presence of an output schema means return values do not need to be explained in the description.
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?
The schema only defines 'date' as a string with no format information, and schema description coverage is 0%. The description compensates by specifying the exact expected format (YYYY-MM-DD). For a single-parameter tool, this fully clarifies the input requirement.
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 states a specific verb and resource ('Get full sleep data') and indicates it provides all details. It also distinguishes the tool from the sibling get_sleep_summary by framing this as the detailed alternative, so an agent can differentiate between them without examining schemas.
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?
The description explicitly names the sibling tool get_sleep_summary and provides the selection criterion: use that tool when a compact summary is desired. This clearly signals when to prefer the alternative, effectively telling the agent when this tool is the right choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.