Skip to main content
Glama

List Athlete Clubs

strava_list_athlete_clubs
Read-onlyIdempotent

Page through stored clubs the athlete belongs to. Refresh fetches all upstream pages; local per_page does not cap API request cost.

Instructions

Page through stored clubs the athlete belongs to. Refresh fetches all upstream pages; local per_page does not cap API request cost.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "strava_list_athlete_clubs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoLocal page number (1-1000000, default 1); upstream refresh may traverse all pages
per_pageNoResults per page (1-200, default 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.4.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / page / description
      Previous value: -"Page number (default 1)"New value: +"Local page number (1-1000000, default 1); upstream refresh may traverse all pages"
    • addedInput schema / properties / page / maximum
      Added value: +1000000
  2. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnly/idempotent/openWorld/no-destructive, so the bar is lower; the description still adds real context by disclosing that results are locally stored and that per_page caps local paging only, not upstream API cost. The unexplained 'Refresh' concept is a minor ambiguity but not a contradiction of the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action, with the cost caveat placed where it matters. The reference to 'Refresh' (a mechanism not represented in the schema) is the one element that costs the reader a beat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, no-required-arg read tool with full annotation coverage and no output schema, this is nearly sufficient: scope, storage model, and pagination cost behavior are all covered. Left unexplained are what a refresh implies for callers and what a club entry contains.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above baseline by clarifying that per_page governs local page size and does not bound upstream request cost, meaning the schema's 'Results per page' line alone would not convey. It adds no detail on page numbering beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (page through) and resource (clubs the athlete belongs to) and signals that results come from stored/local data, which separates it from strava_get_club (single club lookup) and strava_list_activities. It never names a sibling explicitly, so differentiation is inferred rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the pagination language (use page/per_page to walk results), and the mention of refresh suggests when data may be stale. But there is no explicit when-to-use guidance, no pointer to strava_sync_status or strava_get_club, and no statement of when a refresh is needed versus already done.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.