Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_menstrual_day

Read-only

Fetches menstrual-cycle day records for a date range, with optional analysis and a prediction reference date; ranges default to 7 days and cap at 31 days.

Instructions

Menstrual-cycle day view, including optional analysis and prediction reference date. Raw JSON fields are not normalized. Date ranges default to 7 days and allow at most 31 days (activity search uses pagination).

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

Input Schema

Name	Required	Description	Default
`skipbm`	No
`today_date`	No
`calendar_date`	No
`include_analysis`	No
`reduced_response`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 26, 2026

TDQS

C2.6/5.0

Behavior3/5

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

Annotations already declare a safe, read-only, open-world operation, so the description only adds the useful behavioral notes that raw JSON is not normalized and that date ranges default to 7 and cap at 31 days. It says nothing about per-day uniqueness, empty-date behavior, or what 'analysis' entails, and the pagination remark is confusing noise.

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?

It is short and the core ('menstrual-cycle day view') is front-loaded, but the final clause about activity search pagination does not belong and wastes a third of the definition.

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

Completeness2/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 values need no explanation, but with 5 completely undocumented parameters the definition leaves the agent unable to choose date arguments or understand reduced_response/skipbm. Given the sibling menstrual_summary and the 31-day cap, more context was needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 5 parameters, so the description must carry the full explanation, and it does not. It vaguely gestures at 'optional analysis' and 'prediction reference date', but skipbm, reduced_response, and the distinction/format between today_date and calendar_date are entirely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('Menstrual-cycle day view') and the scope (single day plus optional analysis), which is more specific than the bare name. However, it uses a noun phrase rather than a verb and never distinguishes itself from the sibling 'garmin_api_menstrual_summary', leaving an agent to guess when a day view is preferred over a summary.

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 a hard limit ('at most 31 days', default 7) but gives no guidance on when to call this instead of menstrual_summary or the other day-scoped tools. The trailing '(activity search uses pagination)' is boilerplate unrelated to this tool and actively muddies usage guidance.

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