Skip to main content
Glama
Sign In
garmin-mcp

garmin-mcp

by konstantintutsch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_activity_details

Read-only

Fetch detailed Garmin Connect activity data by activity ID, including GPS polyline and chart points, to analyze or review a workout. Read-only; dates use YYYY-MM-DD.

Instructions

Return activity details. (Garmin Connect, read-only. Dates are YYYY-MM-DD.)

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_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxpolyNo
maxchartNo
activity_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the description repeating "read-only" adds nothing. The only new content, "Dates are YYYY-MM-DD," is a formatting hint for a tool that has no date parameters, and the meaning of maxpoly/maxchart (likely response-size caps) is never disclosed.

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 short and front-loaded, but the brevity comes from omission rather than precision. The parenthetical date-format note is wasted text that could mislead an agent into searching for a date parameter.

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?

An output schema exists so return values need not be explained, but the description still leaves an agent unable to tell this apart from sibling activity tools or to understand two of its three parameters. For a tool whose main risk is picking the wrong activity-detail endpoint, this is insufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across all three parameters. The description never mentions activity_id (required, integer-or-string) nor the opaque maxpoly/maxchart parameters, and the date-format note does not map to any actual argument. With low coverage, the description was required to compensate and does not.

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?

"Return activity details" essentially restates the tool name without specifying what 'details' means. Among ~15 get_activity_* siblings (get_activity, get_activity_splits, get_activity_weather, get_activity_gear, etc.), nothing distinguishes this tool's scope or payload from any of them.

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 get_activity, get_activity_splits, or download_activity. "read-only" is a safety property, not usage guidance, and no prerequisites or next steps are offered.

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