Skip to main content
Glama

garmin_womens_health

Read-only

Retrieve pregnancy summaries, menstrual data for a specific date, or a menstrual calendar for a date range from Garmin Connect.

Instructions

Pregnancy summary, menstrual data for one date, or the menstrual calendar for a range.

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": {
      "kind": "<kind>"
    },
    "name": "garmin_womens_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoYYYY-MM-DD, 'today' or 'yesterday'
kindYes
end_dateNoYYYY-MM-DD, 'today' or 'yesterday'
start_dateNoYYYY-MM-DD, 'today' or 'yesterday'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and network scope are covered. The description adds the useful behavioral fact that output granularity varies by mode (one summary vs. single date vs. a range), but says nothing about what happens when a date has no data or a cycle is not tracked, which is the likely failure mode here.

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?

A single compact sentence with no filler, and the three modes are listed in the same order as the enum. It is slightly telegraphic — a fragment rather than a complete sentence — which costs a little clarity but not much length.

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?

For a four-parameter read-only tool with no output schema, the definition covers purpose and mode selection adequately, and annotations plus schema carry the rest. The remaining gap is the unstated mapping between modes and their required date parameters, which matters because all three date fields are optional.

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 75%, and notably the `kind` enum itself carries no per-value description in the schema, so the description's enumeration of the three modes does add real meaning beyond structured data. However, it never ties `date` to `menstrual_day` or `start_date`/`end_date` to `menstrual_calendar`, leaving the agent to guess which optional date fields each mode consumes.

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 names the resource (pregnancy summary, menstrual data, menstrual calendar) with a clear verb-less retrieval framing, and the three listed modes map one-to-one onto the `kind` enum values. It is distinguishable from siblings like garmin_wellness or garmin_body, though it never states explicitly that it retrieves Garmin women's health data rather than computing or summarizing it locally.

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?

Listing three modes implies the selection logic (pick `kind` matching the data you want), but there is no explicit when-to-use guidance, no mention of prerequisites such as a paired device or logged cycle data, and no routing away from related siblings. The agent must infer that `pregnancy` is a whole-record summary while the other two are date-scoped.

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