Skip to main content
Glama
Sign In
Strava Planner MCP

Strava Planner MCP

by Mohith1612
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Strava Activity

getActivity
Read-only

Retrieve complete Strava activity details, including metric splits and embedded laps, using an activity ID.

Instructions

Use after finding an activity ID. Returns full activity detail including metric splits and embedded laps when Strava provides them.

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": {
      "activityId": "<activityId>"
    },
    "name": "getActivity"
  }
}

Input Schema

NameRequiredDescriptionDefault
activityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, which the description does not contradict. Description adds behavioral detail that metric splits and embedded laps are returned 'when Strava provides them', indicating optional content.

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?

Single sentence, front-loaded with usage context, no wasted words. Achieves maximum conciseness.

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 1-parameter, read-only tool, the description covers main purpose and return content hints. Could mention error handling, but is largely complete.

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

Parameters2/5

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

Schema coverage is 0% and the description only indirectly mentions the parameter ('after finding an activity ID'). It does not add explicit details about the activityId parameter beyond the schema constraints.

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 it returns full activity detail including metric splits and embedded laps. The verb 'Returns' and resource 'activity' match the tool name, and it distinguishes from sibling tools like getActivityLaps.

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

Usage Guidelines4/5

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

The phrase 'Use after finding an activity ID' provides clear prerequisite context. It implies this is the primary detail endpoint, but does not explicitly state when not to use it vs. siblings like getActivityStreams.

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