Skip to main content
Glama
Sign In
Strava Planner MCP

Strava Planner MCP

by Mohith1612
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Strava Athlete Overview

getAthleteOverview
Read-only

Retrieve a compact training overview and recent trends for an athlete over a custom look-back window.

Instructions

Returns a compact training overview and recent trends over a bounded look-back window (default last 365 days). Pass sinceDays or an explicit after for a different window.

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": "getAthleteOverview"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoUnix seconds; overrides sinceDays when set.
sinceDaysNoLook-back window in days (max 5 years).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true; the description adds that it returns a compact overview and recent trends, but does not detail other behavioral aspects like data recency or computation cost.

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?

Two sentences, no filler, front-loaded with the main purpose and essential usage guidance.

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 read tool with no required parameters and no output schema, the description adequately covers the tool's purpose and parameter usage, though the exact contents of the overview are unspecified.

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% with descriptions for both parameters. The description adds meaningful context by explaining the relationship between `sinceDays` and `after` and the default window, going beyond the schema.

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 clearly states 'Returns a compact training overview and recent trends over a bounded look-back window' with specific verb and resource, and distinguishes from sibling tools like getTrainingHistory and getRecentActivities.

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?

Provides guidance on using parameters to adjust the time window but does not explicitly state when to use this tool versus alternatives, nor when not to use it.

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