Garmin MCP for macOS

Overview Schema Source Related Servers Discussions Admin

garmin_api_menstrual_summary

Read-only

Retrieves a menstrual-cycle summary for a specified calendar date, defaulting to a 7-day range and allowing up to 31 days. Use it to query cycle tracking data from Garmin Connect.

Instructions

Menstrual-cycle summary for a 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_summary"
  }
}

Input Schema

Name	Required	Description	Default
`calendar_date`	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.9/5.0

Behavior3/5

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

Annotations already declare read-only, open-world, and non-destructive behavior. The description adds useful context that raw JSON fields are not normalized and that date ranges default to 7 days with a 31-day maximum, though the pagination remark seems tangential.

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 description is brief and front-loads the purpose, but the parenthetical about activity search pagination does not clearly earn its place in a menstrual-summary tool definition.

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

Completeness3/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 not be described, and annotations cover safety. However, the description leaves calendar_date semantics and the distinction from garmin_api_menstrual_day unclear, which are important for correct invocation.

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% for the single calendar_date parameter, so the description must compensate, but it only discusses unspecified 'date ranges' rather than explaining calendar_date's expected format or semantics. The range constraints are relevant but leave the actual parameter meaning ambiguous.

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?

The description clearly identifies the resource ('Menstrual-cycle summary') and implies retrieval for a given date. It is distinguishable as a menstrual-cycle tool, but it does not clarify how it differs from the sibling garmin_api_menstrual_day.

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 constraints on date ranges but gives no explicit guidance on when to use this tool versus garmin_api_menstrual_day or other summary tools. The agent must infer usage context.

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