Skip to main content
Glama
Sign In
garmin-connect-mcp

garmin-connect-mcp

by Samiu1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get User Profile Settings

garmin_get_user_profile
Read-onlyIdempotent

Get Garmin Connect profile settings and unit preferences to know whether measurements should be presented as metric or statute. Call it before other data when display units matter.

Instructions

Get the user's Garmin Connect profile settings: display name, locale, time zone, and the unit preferences that other responses are expressed in.

Call this first when units matter. measurementSystem tells you whether the user thinks in metric or statute, and powerFormat, heartRateFormat, hydrationMeasurementUnit, and glucoseMeasurementUnit give the per-metric display units. Garmin returns distances in meters and durations in seconds regardless, so this is about how to present them.

Note: this endpoint carries no device or sensor information. The Personal API exposes no device inventory, so which metrics a user has is discovered by requesting them; garmin_get_daily_health reports what came back.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "garmin_get_user_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
response_formatNo'markdown' for readable text, 'json' for the exact Garmin field names and valuesmarkdown
include_empty_fieldsNoKeep fields Garmin returned as null or empty. Off by default, since unsupported sensors on the user's device produce large runs of nulls. Turn on only to inspect raw shape.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered; the description goes further by disclosing a real behavioral nuance: Garmin returns distances in meters and durations in seconds regardless of the user's display preference. It also states a negative scope fact (no device inventory exists in the Personal API) that would otherwise cost an agent a failed call.

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

Conciseness4/5

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

Front-loaded with the resource definition and the primary usage trigger, then the units caveat, then the negative-scope note. Each sentence carries information, though the closing note paragraph is slightly long relative to what it contributes.

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

Completeness5/5

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

There is no output schema, so the description must carry the return contract — and it does, naming the exact kinds of fields returned and how units should be interpreted downstream. For a two-parameter read tool it leaves nothing an agent needs unresolved.

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?

Schema description coverage is 100%, so response_format and include_empty_fields are already fully documented, including the enum and defaults. The description adds no additional meaning about either parameter, so the baseline 3 applies.

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?

States a specific verb and resource (get the user's Garmin Connect profile settings) and enumerates the returned content: display name, locale, time zone, and unit preferences. It also explicitly bounds the tool against siblings by noting it carries no device or sensor information, so an agent can distinguish it from garmin_get_daily_health without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition — 'Call this first when units matter' — and names the concrete decision it enables (metric vs statute thinking, per-metric display units). It also names the alternative path for device metric discovery (request them; garmin_get_daily_health reports what came back), which is the right routing for that need.

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