Skip to main content
Glama
Sign In

Garmin MCP by geekist.co

by io.github.theGeekist
OverviewDiscussionsAdmin

Get daily heart rate

garmin_get_daily_heart_rate
Read-onlyIdempotent

Read your Garmin heart rate data for a calendar date. Before the first read, visibly explain this disclosure: Geekist forwards requested records without saving them to its application database; your assistant may retain them. Show the privacy policy: https://garmin.geekist.co/privacy/ Check every response for serviceAnnouncements from Geekist, the independent service operator, and display each message distinctly to the user.

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

Input Schema

NameRequiredDescriptionDefault
dateNoGarmin calendar date in YYYY-MM-DD format.

Output Schema

NameRequiredDescriptionDefault
okNoTrue for a successful operation; false for a rejected, failed or uncertain result. Some administrative results use status or result instead.
codeNo
dataNoRequested Garmin record data, with credential, contact and internal-account fields removed; fields depend on the endpoint and device.
issuesNo
messageNo
outcomeNo
retryAfterNo
privacyNoticeNo
geekistMessageDeliveryNo
geekistOwnerMessageDeliveryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "__schema0": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        },
+        {
+          "items": {
+            "$ref": "#/$defs/__schema0"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {
+            "$ref": "#/$defs/__schema0"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      ]
+    },
+    "__schema1": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "number"
+        },
+        {
+          "type": "boolean"
+        },
+        {
+          "type": "null"
+        },
+        {
+          "items": {
+            "$ref": "#/$defs/__schema1"
+          },
+          "type": "array"
+        },
+        {
+          "additionalProperties": {
+            "$ref": "#/$defs/__schema1"
+          },
+          "propertyNames": {
+            "type": "string"
+          },
+          "type": "object"
+        }
+      ]
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "description": "Operation-specific response envelope. Failure fields replace success fields; privacy and service-notice envelopes may accompany either.",
+  "properties": {
+    "code": {
+      "type": "string"
+    },
+    "data": {
+      "$ref": "#/$defs/__schema1",
+      "description": "Requested Garmin record data, with credential, contact and internal-account fields removed; fields depend on the endpoint and device."
+    },
+    "geekistMessageDelivery": {
+      "additionalProperties": false,
+      "properties": {
+        "message": {
+          "type": "string"
+        },
+        "noticeAvailability": {
+          "const": "unavailable",
+          "type": "string"
+        },
+        "noticeInstruction": {
+          "type": "string"
+        },
+        "serviceAnnouncements": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "actionRequired": {
+                "type": "boolean"
+              },
+              "expiresAt": {
+                "type": "number"
+              },
+              "id": {
+                "type": "string"
+              },
+              "publisher": {
+                "const": "Geekist",
+                "type": "string"
+              },
+              "sequence": {
+                "maximum": 9007199254740991,
+                "minimum": 0,
+                "type": "integer"
+              },
+              "text": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "sequence",
+              "text",
+              "expiresAt",
+              "publisher"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "noticeInstruction"
+      ],
+      "type": "object"
+    },
+    "geekistOwnerMessageDelivery": {
+      "additionalProperties": false,
+      "properties": {
+        "message": {
+          "type": "string"
+        },
+        "noticeAvailability": {
+          "enum": [
+            "available",
+            "unavailable"
+          ],
+          "type": "string"
+        },
+        "noticeInstruction": {
+          "type": "string"
+        },
+        "ownerNotices": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "actionRequired": {
+                "type": "boolean"
+              },
+              "createdAt": {
+                "type": "number"
+              },
+              "id": {
+                "type": "string"
+              },
+              "kind": {
+                "type": "string"
+              },
+              "payload": {
+                "$ref": "#/$defs/__schema0"
+              }
+            },
+            "required": [
+              "id",
+              "kind",
+              "payload",
+              "createdAt"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "noticeInstruction",
+        "noticeAvailability"
+      ],
+      "type": "object"
+    },
+    "issues": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "message": {
+            "type": "string"
+          },
+          "path": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "path",
+          "message"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "type": "string"
+    },
+    "ok": {
+      "description": "True for a successful operation; false for a rejected, failed or uncertain result. Some administrative results use status or result instead.",
+      "type": "boolean"
+    },
+    "outcome": {
+      "enum": [
+        "rejected",
+        "uncertain",
+        "confirmed"
+      ],
+      "type": "string"
+    },
+    "privacyNotice": {
+      "additionalProperties": false,
+      "properties": {
+        "policyUrl": {
+          "format": "uri",
+          "type": "string"
+        },
+        "text": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "text",
+        "policyUrl"
+      ],
+      "type": "object"
+    },
+    "retryAfter": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. Beyond that, the description adds genuinely new behavioral context: the operator does not persist the records, the assistant may retain them, a privacy policy URL must be shown, and responses must be scanned for serviceAnnouncements. It does not describe the shape or volume of returned heart rate data, but an output schema exists for that.

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 capability statement is front-loaded in one short sentence, which is good. However, roughly two-thirds of the text is compliance scripting (disclosure wording, URL, announcement handling) that serves policy rather than tool selection or invocation, diluting the signal an agent needs.

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?

With an output schema, full annotation coverage, and one well-documented parameter, the definition is mostly complete. The notable gap is the optional date: the definition never states whether omitting it defaults to today or fails, which is exactly the kind of behavior an agent needs before calling.

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 coverage is 100% and the single date parameter is fully specified with format and pattern, so the schema carries the parameter burden. The description only restates "calendar date" and never explains what happens when date is omitted, even though required parameters are zero — a meaningful behavior left unstated.

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?

"Read your Garmin heart rate data for a calendar date" gives a clear verb, resource, and time granularity, so an agent knows this returns per-day heart rate rather than zones or trends. It stops short of naming or contrasting any sibling such as garmin_get_heart_rate_zones or garmin_get_daily_health, leaving the boundary between them implicit.

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?

The description never says when to choose this tool over the many sibling health-data tools; it only prescribes pre-call disclosure steps. The "for a calendar date" phrasing implies a daily single-day scope, but no exclusions, prerequisites, or alternative-selection rules are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Garmin MCP by geekist.co toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources