Skip to main content
Glama
garmin-connect-mcp

garmin-connect-mcp

by Samiu1

Get Menstrual Cycle Data

garmin_get_menstrual_cycle
Read-onlyIdempotent

Retrieve Garmin Connect menstrual cycle data for a date, returning either a cycle summary with phase and predictions or a detailed daily log of symptoms, flow, and baby movement entries.

Instructions

Get menstrual cycle tracking data for a date.

view="summary" returns the cycle summary for the date, with cycle phase and prediction context. view="day_view" returns the detailed per-day log, which can include symptoms, flow, and pregnancy-mode baby movement (kick count) entries.

This data exists only when the user tracks cycles in Garmin Connect. An empty result means tracking is not enabled or no entry exists for that date, not a zero reading.

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

Input Schema

NameRequiredDescriptionDefault
dateNoCalendar date to retrieve, YYYY-MM-DD. Defaults to today.2026-11-15
viewNo'summary' for the cycle summary, 'day_view' for the detailed daily logsummary
today_dateNoday_view only: the current date, used as the reference point for predictions. Defaults to today.
response_formatNo'markdown' for readable text, 'json' for the exact Garmin field names and valuesmarkdown
include_analysisNoday_view only: include cycle analysis alongside the day's log
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.
include_baby_movementNoday_view only: include baby movement (kick count) entries, used in pregnancy mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / date / default
      Previous value: -"2026-11-13"New value: +"2026-11-15"
  2. First observedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description's real contribution is the data-availability caveat: data exists only if the user tracks cycles in Garmin Connect, and an empty result means tracking is off or no entry exists rather than a zero reading. That is a meaningful behavioral disclosure that prevents a common misinterpretation. It stops short of describing response structure or any latency/limit characteristics.

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

Conciseness5/5

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

Three short paragraphs, front-loaded with the core action, then view semantics, then the empty-result caveat. Every sentence carries information an agent would otherwise have to guess.

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 no output schema and seven optional parameters, the description does the necessary work of sketching what each view returns and how to read an empty response. It is adequate for correct invocation; only the exact shape of the summary versus day log remains underspecified, which is acceptable given the response_format switch.

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 the schema already documents date, view, today_date, response_format, and the include_* flags; the baseline is 3. The description adds modest meaning by naming what day_view can contain (symptoms, flow, pregnancy-mode kick counts), but adds nothing about prediction reference dates or the null-suppression behavior the schema flags already cover.

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?

States a specific verb and resource ('Get menstrual cycle tracking data for a date') and splits the two retrieval modes with concrete contents for each (cycle phase and prediction context vs. symptoms, flow, kick counts). The resource is distinct enough from the sibling activity/health tools to identify it, though no sibling is named explicitly to route against overlapping daily-health data.

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

Usage Guidelines3/5

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

The description clearly conditions the choice between view="summary" and view="day_view" on what the agent needs, which is useful mode-selection guidance. It gives no explicit when-to-use-this-tool-vs-another guidance relative to siblings such as garmin_get_daily_health, leaving that inference to the agent.

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