get_daily_stepsRetrieve daily step counts for a given date range, automatically splitting requests longer than 28 days into manageable chunks.
Get daily step counts for a date range (max 28 days per request, auto-chunked for longer ranges).
| Name | Required | Description | Default |
|---|---|---|---|
| endDate | Yes | End date in YYYY-MM-DD format (required) | |
| startDate | Yes | Start date in YYYY-MM-DD format (required) |
Changes observed during successful MCP inspections.
v4.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses behavior beyond annotations, such as auto-chunking for long ranges and the 28-day limit. Annotations already indicate read-only, and the description adds these practical behavioral details.
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?
One concise sentence with the main action upfront and a parenthetical for limits. No unnecessary words, well-structured.
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?
Description conveys the data returned (daily step counts) and a key usage constraint (max range). No output schema exists, so return details are not required, but the description is sufficiently informative for typical usage.
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?
Description clarifies that startDate and endDate define a date range, but does not specify inclusivity, ordering, or additional constraints. Schema provides format via regex but no semantic detail beyond that. Adds some context but not comprehensive.
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?
Description clearly states the action (get daily step counts) and the resource (step data) for a date range, with specific constraints. It distinguishes from sibling tools by focusing on daily steps specifically.
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?
Provides usage constraints (max 28 days, auto-chunking) but does not explicitly mention when to use this tool over other step-related getters (e.g., get_steps_data, get_daily_summary). Guidance is implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.