Skip to main content
Glama
Sign In
garminconnect-js

garminconnect-js

by DynamicsNinja
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

confirm_menstrual_period_start

Confirms that a menstrual period started on a date, including period and cycle lengths, in Garmin Connect. Requires cycle tracking setup; this action cannot be undone.

Instructions

Confirms that a period started on a date, with its period and cycle lengths. There is no undo. Needs cycle tracking set up in Garmin Connect first. POSTs /periodichealth-service/menstrualcycle/{periodStartDate} directly, NOT the dayview/calendar/lastconfirmed/summary sub-paths.

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": {
      "periodStartDate": "<periodStartDate>",
      "periodLength": "<periodLength>",
      "cycleLength": "<cycleLength>"
    },
    "name": "confirm_menstrual_period_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNo
cycleLengthYes
periodLengthYes
periodStartDateYesCalendar date, YYYY-MM-DD (UTC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely new context — irreversibility ('There is no undo') and the setup prerequisite. No permission/auth details, but the write nature and irreversibility are covered.

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-loads the core action, then adds the critical caveats and endpoint detail in order of importance. The endpoint-path sentence is dense but earns its place by preventing calls to the wrong sub-paths.

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 write tool with no output schema and terse annotations, the description covers the key facts an agent needs: prerequisite, irreversibility, and target endpoint. It falls short only on parameter-level detail (units/meaning) for the low-coverage schema.

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 only 25% and three params are required, so the description must compensate. It loosely maps 'period and cycle lengths' to periodLength/cycleLength but adds no units, ranges, or meaning for options.predictedCycle. Marginal compensation for a low-coverage schema.

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 (confirms) and resource (menstrual period start) with the payload it carries (period and cycle lengths). It is clearly distinguishable from siblings like init_menstrual_cycle_setup, update_menstrual_calendar, and get_menstrual_last_confirmed.

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?

Gives an explicit prerequisite (cycle tracking must be set up in Garmin Connect first) and a strong caution (no undo). It doesn't name specific alternative tools to call instead, but the endpoint sentence routes the agent away from the wrong sub-paths.

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

Deploy Server

Other Tools