Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_activity_splits

Read-only

Retrieve lap splits for a Garmin activity using its ID. Analyze pacing and performance for each segment without manual data extraction.

Instructions

An activity's laps.

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

NameRequiredDescriptionDefault
activityIdYesNumeric id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that — no note on return shape, pagination, or what a 'split' contains relative to sibling endpoints.

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

Conciseness3/5

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

It is extremely short and wastes no words, but it is under-specified rather than well-structured — a bare noun phrase rather than a front-loaded statement of action and scope.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 annotations and full schema coverage this could be adequate, but in a suite containing get_activity_splits, get_activity_split_summaries, and get_activity_typed_splits the description must explain the distinction and does not. An agent cannot confidently select this endpoint.

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?

Only one parameter (activityId) with 100% schema description coverage, so the schema carries the burden and the baseline of 3 applies. The description adds no meaning about the id format (integer or string) or any filtering behavior.

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

Purpose2/5

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

The description is the fragment 'An activity's laps.' — essentially a restatement of the tool name ('splits' ≈ 'laps') with no verb and no scope. It does not distinguish this tool from close siblings such as get_activity_split_summaries or get_activity_typed_splits, leaving the agent unable to tell which split-related endpoint to choose.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the three look-alike siblings (get_activity_split_summaries, get_activity_typed_splits, get_activity_details) that an agent must disambiguate against. Nothing misleading, but nothing helpful either.

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