Garmin Connect MCP Server

Get Activity Splits

get_activity_splits

Read-only

Retrieve split and lap data for a specific activity to analyze pace, distance, and time for each segment.

Instructions

Get split/lap data for a specific activity including pace, distance, and time for each split.

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

Input Schema

Name	Required	Description	Default
`activityId`	Yes	The unique activity identifier (required)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.3.0Jul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already communicate read-only safety, so the bar is lower. The description usefully adds the specific returned data scope (pace, distance, and time per split) and no contradictory side effects are claimed. It does not cover things like units, availability, or authorization, but those are less critical for a simple read-only fetch.

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 sentence, front-loads the action, and contains no filler or repetition. Every word contributes to understanding what the tool does and returns.

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?

This is a low-complexity tool with one parameter and no output schema, so a single clarifying sentence is nearly sufficient. The description names the return attributes (pace, distance, time) but leaves minor ambiguity about split types and units, which the sibling get_activity_typed_splits could have helped clarify.

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?

The schema already covers activityId fully as the required identifier with 100% description coverage. The tool description adds no information about parameter format, default behavior, values, or edge cases, so the neutral baseline of 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 a specific verb ('Get') and identifies the resource ('split/lap data') scoped to a specific activity, while also naming the key returned attributes (pace, distance, time). This clearly distinguishes it from generic activity listing tools, though not from get_activity_typed_splits.

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?

The description implies this tool is for fetching per-split data for one activity via a required activityId, but it does not explicitly state when to prefer this over alternatives such as get_activity_typed_splits or get_activity_details. No exclusions or alternative tool names are provided.

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

Deploy Server