Skip to main content
Glama
durely insights
by durely

Menstrual cycle

garmin_get_womens_health
Read-onlyIdempotent

Fetch Garmin Connect menstrual cycle data for a date, including cycle day, phase, predictions, fertile window, ovulation, and symptoms. Review daily reproductive health or check cycle tracking setup.

Instructions

Get menstrual cycle tracking from Garmin Connect for a date: cycle day, current phase and days until the next, period and cycle length, predicted next cycle, fertile window and ovulation date, plus that day's logged symptoms and notes (day view). Fetched live from Garmin.

Returns a clear "not tracked" message when cycle tracking isn't set up. Defaults to today.

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

Input Schema

NameRequiredDescriptionDefault
dateNoDefaults to today
response_formatNo'markdown' for readable text (default), 'json' for complete structured datamarkdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, lowering the bar. The description still adds genuine context: 'Fetched live from Garmin' (reinforces openWorld and warns of network dependence) and, more importantly, that it returns a clear 'not tracked' message when cycle tracking isn't set up — an empty-state behavior the annotations cannot express.

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 and payload, then the empty-state caveat, then the default date. All sentences earn their place; the only slight redundancy is 'Defaults to today', which the schema also states.

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 carries the return-value burden — and it discharges it by enumerating every field the call yields plus the not-tracked fallback. With two well-documented parameters and a safety profile already in annotations, an agent has everything needed to call this correctly.

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 'date' parameter already documents its default and pattern; the description's 'Defaults to today' and 'day view' merely restate that. The response_format enum is untouched in the description, so it adds essentially nothing beyond the structured schema. Baseline 3 is correct.

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 (Get) and a unique resource (menstrual cycle tracking), then enumerates exactly the fields returned: cycle day, phase, period/cycle length, predicted next cycle, fertile window, ovulation date, symptoms and notes. No sibling tool covers this domain, so it is trivially distinguishable from garmin_get_daily_health or garmin_get_body_composition.

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

Usage Guidelines4/5

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

The '(day view)' qualifier and 'Defaults to today' give the agent clear context for when this is the right call: a single date's cycle state. It stops short of naming alternatives or an explicit when-not, but no sibling overlaps enough to need that routing.

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