get_coursesFetch saved courses and routes from Garmin Connect, using limit and start offset to paginate through results.
Get saved routes/courses from Garmin Connect.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of courses to return (default: 20) | |
| start | No | Starting index for pagination (default: 0) |
Changes observed during successful MCP inspections.
v4.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, so the description need not repeat safety. It adds no additional behavioral context, such as pagination behavior or return format, but such details are partially in the schema. With annotations covering safety, a baseline 3 is appropriate.
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 sentence with no filler, front-loading the core purpose. It is highly concise.
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 list retrieval tool with two optional parameters and no output schema, the description minimally states the purpose. It lacks an explicit mention of the return type (list of courses) but that is implied. Given the low complexity and presence of annotations, it is reasonably complete.
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 input schema fully documents both parameters (limit and start) with descriptions, so the description adds no additional parameter semantics. Per the rubric, with >80% schema coverage, baseline 3 applies.
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 'Get saved routes/courses from Garmin Connect.' which specifies the action (get) and the resource (saved routes/courses), distinguishing it from other get_* tools that focus on different data types.
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 usage guidance is provided. The description does not mention when to use this tool versus other get_* tools, nor any exclusions or alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.