Retrieve scheduled Garmin Connect workouts and calendar entries for a month, defaulting to the current month, to review or plan training.
Scheduled workouts / calendar for a month (defaults to the current month).
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Year, e.g. 2026. Default: current year. | |
| month | No | Month 1-12. Default: current month. |
Changes observed during successful MCP inspections.
v1.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations, so the description carries the full burden. It discloses the default-month behavior but nothing about return format, whether the calendar is sparse or filled, auth needs, or pagination. 'Calendar' hints at structure but is not elaborated.
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?
Single short sentence, front-loaded with the resource and default. Efficient, though the slash phrasing is slightly terse.
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?
Adequate for a 2-param read whose schema is fully covered, but with no annotations and no output schema, the description leaves the return shape and sibling differentiation to inference.
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 coverage is 100%, so both year and month are fully documented with types, bounds, and defaults. The description only restates the default-month behavior already present in the schema.
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 relationship: retrieving scheduled workouts as a calendar for a month. It's distinguishable from get_workouts (likely completed sessions) by the 'scheduled' qualifier, though it doesn't explicitly name the contrast.
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 indication of when to use this vs get_workouts or get_training. The calendar/month framing implies a schedule view, but no exclusions or alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.