Skip to main content
Glama
Sign In

Garmin MCP by geekist.co

by io.github.theGeekist
OverviewDiscussionsAdmin

Get body battery history

garmin_get_body_battery_history
Read-onlyIdempotent

Read your daily Garmin Body Battery reports across a date range. 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_body_battery_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
chunksNoGarmin chunk parameter for the daily Body Battery report.
endDateNoLast calendar date in YYYY-MM-DD format.
startDateNoFirst 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. Changed3 schema fields changed
    • addedInput schema / properties / chunks / description
      Added value: +"Garmin chunk parameter for the daily Body Battery report."
    • changedInput schema / properties / endDate / description
      Previous value: -"Garmin calendar date in YYYY-MM-DD format."New value: +"Last calendar date in YYYY-MM-DD format."
    • changedInput schema / properties / startDate / description
      Previous value: -"Garmin calendar date in YYYY-MM-DD format."New value: +"First calendar date in YYYY-MM-DD format."
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it states Geekist does not persist the forwarded records, warns the assistant may retain them, and discloses that responses may carry serviceAnnouncements that must be surfaced. It stops short of describing pagination or the shape of the returned report, and leaves the 'chunks' parameter behavior unexplained.

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 purpose is front-loaded in the first sentence, which is good. However, the majority of the text is disclosure/announcement boilerplate rather than information about invoking the tool, and the unexplained 'chunks' parameter receives no attention at all.

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

Completeness4/5

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

With an output schema present, the description need not document return values, and it correctly focuses on purpose, data-handling behavior, and the serviceAnnouncements obligation. For a simple three-parameter read tool this is nearly complete, missing only date-range limits or pagination expectations.

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 startDate, endDate and chunks are already documented in the schema, and the description adds no format, boundary, or interaction details beyond that. Baseline 3 applies when the schema carries the parameter burden.

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 daily Garmin Body Battery reports across a date range" gives a specific verb (read), a specific resource (Body Battery daily reports), and a scope (date range). Body Battery is a distinguishable data domain from sibling tools like garmin_get_steps_history or garmin_get_sleep_history, though the description never names an alternative to disambiguate.

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?

It states the range-based read pattern but gives no guidance on when this tool is preferable to related wellness/history tools, nor any exclusions or prerequisites for the date range (e.g., maximum span). The only procedural guidance is compliance-oriented (show privacy policy, display serviceAnnouncements), not tool-selection guidance.

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