Skip to main content
Glama
Sign In
Strava Planner MCP

Strava Planner MCP

by Mohith1612
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get Strava Activity Zones

getActivityZones
Read-only

Retrieve heart-rate or power zones for a specific Strava activity to analyze time spent in each zone.

Instructions

Use for time-in-zone analysis. Returns heart-rate or power zones when Strava exposes them for the athlete and activity.

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

Input Schema

NameRequiredDescriptionDefault
activityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Adds beyond readOnlyHint: clarifies zones only when Strava exposes them. Does not detail error conditions or empty returns, but adequate for a read-only tool.

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 efficient sentences, front-loaded, no redundant information.

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?

Adequate for a simple tool with one parameter and no output schema, but could benefit from a note on return structure or availability conditions.

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?

With 0% schema coverage, description adds no meaning to the activityId parameter. Should specify that it refers to a Strava activity ID.

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?

Clearly states it returns heart-rate or power zones for time-in-zone analysis, distinguishing it from other activity tools. Could be more explicit about sibling differentiation.

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 the context 'time-in-zone analysis' but lacks guidance on when not to use it or alternatives 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