Fetch aggregate stats for a Strava athlete by ID. Get totals for distance, time, and achievements to assess performance at a glance.
Fetch aggregate stats for a Strava athlete id.
| Name | Required | Description | Default |
|---|---|---|---|
| athleteId | Yes | Strava athlete id. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already communicates the read-only nature, and the description's use of 'Fetch' is consistent. The phrase 'aggregate stats' adds a small amount of context about the returned data being summarized, but it does not disclose what specific stats are included or any behavior beyond the annotation.
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 one concise sentence that immediately states the resource and scope. There is no fluff, and every word earns its place for a tool with a single parameter.
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 simple schema and readOnlyHint, the description is minimally sufficient, but it leaves a gap: 'aggregate stats' is vague and could overlap with sibling tools like strava_athlete_zones. Without an output schema, more detail on what stats are returned would improve completeness.
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 description coverage is 100%, so the parameter is fully documented in the schema. The description merely restates 'Strava athlete id' without adding any new meaning, format guidance, or usage nuance.
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 the action ('Fetch') and resource ('aggregate stats for a Strava athlete id'). It distinguishes the tool from siblings like athlete_profile and athlete_zones by focusing on aggregate statistics, though it does not explicitly name alternatives.
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 guidance is provided on when to use this tool versus the many sibling tools, such as strava_athlete_zones or strava_activity_summary. The description gives no context for selection or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.