get_activity_fit_messages
Retrieve and parse an activity's original FIT file messages in file order, with optional message-type filtering and pagination, to access raw device data unmerged with Garmin Connect edits.
Instructions
Retrieve and generically parse an activity's original FIT file.
This is the source-of-truth endpoint for original device activity data.
It returns every message and every field emitted by the FIT decoder
without applying sport-specific curation. Messages remain in file order,
and each field includes its decoded value plus units and definition
number when available. Unknown and duplicate fields are retained.
Garmin Connect edits made after upload may be stored only in Garmin's
service and are not necessarily written back into the original FIT file.
This tool intentionally does not merge those service-side edits.
High-frequency ``record`` messages are counted but omitted by default.
Other message types occurring more than 100 times are also inventoried
but omitted from an unfiltered default response. Request those types
explicitly with message_types. All returned messages are bounded by
message_offset/message_limit (maximum 5000 per call); follow
pagination.next_offset until absent to retrieve the full selected stream.
Use message_types to return only particular FIT message types while
message_counts still inventories the complete file. For example, a
strength workout can usually be inspected efficiently with
["session", "lap", "set", "exercise_title"]. Message type names are
case-insensitive and should use FIT/fitparse snake_case names.
Args:
activity_id: Garmin activity ID.
message_types: Optional list of FIT message types to return. Omit to
return low-frequency non-record message types.
include_records: Include the high-frequency record stream (default false).
message_offset: Zero-based offset within the selected message stream.
message_limit: Maximum messages returned per call, 1-5000 (default 1000).
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_fit_messages"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| activity_id | Yes | ||
| message_limit | No | ||
| message_types | No | ||
| message_offset | No | ||
| include_records | No |