Skip to main content
Glama

get_activity_splits

Read-only

Retrieve lap and nested length splits for a Garmin activity ID, including GMT start-time timestamps for each split.

Instructions

Get splits for an activity

    Lap and nested length start_time_gmt timestamps are GMT (UTC).

    Args:
        activity_id: ID of the activity to retrieve splits for
    

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": {
      "activity_id": "<activity_id>"
    },
    "name": "get_activity_splits"
  }
}

Input Schema

NameRequiredDescriptionDefault
activity_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare this as a non-destructive, read-only, open-world call, so the safety profile is covered. The description adds a genuinely useful semantic detail — that lap and nested length start_time_gmt values are GMT — but says nothing about the shape of the response, ordering, or pagination.

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?

The core sentence is front-loaded and clear, but the 'Args:' block is boilerplate that repeats the parameter name, and the GMT timestamp note appears before the purpose-adjacent detail, making the structure feel like an auto-generated docstring.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-parameter read with no output schema, so a short description is acceptable, and the GMT note hints at the returned lap/length structure. Still, without an output schema the description should say more about what splits are returned, and the parameter ambiguity is left unresolved.

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 one parameter and 0% schema description coverage, the description must carry the burden, yet its 'Args' entry merely restates the field name ('ID of the activity to retrieve splits for'). It does not resolve the schema's ambiguous anyOf of integer or string, so an agent gets no format guidance beyond the field label.

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?

The description names a specific verb and resource ('Get splits for an activity'), which is unambiguous on its own. It does not, however, distinguish itself from close siblings such as get_activity_typed_splits or get_activity_split_summaries, which an agent would need in order to choose correctly.

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 statement of when to use this tool versus the typed-splits or split-summaries alternatives, and no prerequisites or exclusions are given. Usage must be inferred entirely from the name and the single required argument.

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