Skip to main content
Glama

Get daily health

garmin_get_daily_health
Read-onlyIdempotent

Read one selected Garmin health metric for one calendar date. Returns calendarDate, metric and Garmin data; available fields depend on the metric and synced devices. Use garmin_get_daily_summaries for a multi-day summary or a dedicated history tool for a metric over time. 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

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": {
      "date": "<date>",
      "metric": "<metric>"
    },
    "name": "garmin_get_daily_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesCalendar date to retrieve, YYYY-MM-DD, in the user’s context.
metricYesOne health data category to retrieve for the date.

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
metricNo
sourceNo
messageNo
outcomeNo
retryAfterNo
calendarDateNo
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": {
      +    "calendarDate": {
      +      "type": "string"
      +    },
      +    "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"
      +    },
      +    "metric": {
      +      "enum": [
      +        "summary",
      +        "sleep",
      +        "heart_rate",
      +        "hrv",
      +        "body_battery",
      +        "stress",
      +        "steps",
      +        "weight"
      +      ],
      +      "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"
      +    },
      +    "source": {
      +      "const": "Garmin Connect",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"Calendar date to retrieve, YYYY-MM-DD, in the user’s context."
    • addedInput schema / properties / metric / description
      Added value: +"One health data category to retrieve for the date."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description does not contradict them. Beyond that, it discloses non-obvious behavior: available fields vary by metric and synced devices, responses may carry serviceAnnouncements from the third-party operator, and a data-forwarding/privacy disclosure must be surfaced before the first read. These are operational facts an agent cannot infer from the schema or annotations.

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?

The functional purpose and sibling routing are front-loaded in the first two sentences, with no wasted phrasing. The trailing compliance block (disclosure, privacy URL, serviceAnnouncements handling) is long relative to the tool's function, but each sentence carries a distinct actionable obligation rather than filler.

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?

An output schema exists, so return-value documentation is not required, and the description still flags that returned fields are metric- and device-dependent. With only two required, fully documented parameters and complete annotation coverage, nothing an agent needs in order to call this correctly is missing.

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 metric parameter even carries an enum, so the schema already carries parameter meaning. The description only restates the one-metric/one-date framing and adds no format, default, or interpretation detail (e.g., what "summary" aggregates, or how timezone interacts with "date"). Baseline 3 is appropriate.

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?

"Read one selected Garmin health metric for one calendar date" gives a specific verb (read), a specific resource (Garmin health metric) and an explicit cardinality constraint (one metric, one date). This immediately separates it from the multi-metric and multi-day siblings such as garmin_get_daily_summaries or garmin_get_sleep_history.

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?

The description names two concrete alternatives and the conditions that select them: garmin_get_daily_summaries for multi-day summaries, and "a dedicated history tool" for a metric over time. Combined with the single-date/single-metric scoping, an agent knows exactly when this tool is the right pick and when to route elsewhere.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources