Skip to main content
Glama
Sign In
Strava MCP Server

Strava MCP Server

by groundcobra009
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_athlete_stats

Retrieve a Strava athlete's total distance, total time, and other key statistics for performance analysis.

Instructions

アスリートの統計情報（総距離、総時間など）を取得します。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "athlete_id": "<athlete_id>"
    },
    "name": "get_athlete_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
athlete_idYesアスリートのID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden for behavioral disclosure. It states the tool retrieves statistics but does not explicitly disclose it is a read-only operation, nor does it mention side effects, required permissions, or return format. The 'get' verb implies reading, but this is not stated.

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

Conciseness5/5

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

The description is a single concise sentence that is front-loaded with the action and resource, and it includes illustrative examples. Every word earns its place.

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 simple tool with one required parameter and no output schema, the description provides enough context by giving example outputs (total distance, total time) and using 'など' to indicate additional stats. It does not fully enumerate all possible statistics, but it is adequate for a straightforward retrieval tool.

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

Parameters3/5

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

Schema coverage is 100% with a single parameter athlete_id described as 'アスリートのID'. The description does not add much beyond the schema, but because the schema already fully documents the parameter, the baseline 3 is appropriate.

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

Purpose5/5

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

The description uses the specific verb '取得' (get) with the resource 'athlete stats', and provides concrete examples like total distance and total time. It clearly distinguishes from sibling tools such as get_athlete (profile) and get_activity (individual activities).

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

Usage Guidelines2/5

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 alternatives like get_athlete or get_activities, nor does it state any prerequisites or exclusions.

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

Deploy Server

Other Tools