Retrieve a concise list of Garmin Connect activities within an inclusive date range, defaulting to the last 14 days. Use to summarize training history or review recent workouts.
List concise activities in an inclusive date range; defaults to the last 14 days.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| end_date | No | ||
| start_date | No |
| 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, the description carries the behavioral burden and does disclose two useful behaviors: date boundaries are inclusive, and the default window is the last 14 days. It stops short of describing ordering, pagination, the meaning of 'concise', or what the returned activities look like.
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 a single dense sentence that front-loads the core purpose and then adds the key default behavior. Every word earns its place; there is no repetition or filler.
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 three-parameter list tool, the description is reasonably complete, but gaps remain: no mention of limit behavior, no output shape, and no guidance on how this tool relates to its siblings. It is sufficient for basic use but not fully self-contained.
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?
With 0% schema description coverage, the description must compensate for the schema's bare property names. It adds meaningful semantics for start_date and end_date by specifying inclusivity and the default range, but it says nothing about the limit parameter or acceptable date formats.
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 names the action ('List'), the resource ('concise activities'), and the scope ('inclusive date range; defaults to the last 14 days'). It is specific and understandable, but it does not explicitly differentiate get_activities from sibling tools like get_recent_activities or compare_activities.
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 implies usage: call it to list activities within a date range, and call it with no arguments to get the last 14 days. However, it never mentions when to prefer get_recent_activities, compare_activities, or get_cycle, nor does it state any exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.