Skip to main content
Glama

get_menstrual_calendar_data

Read-only

Fetch menstrual calendar data between two dates; requests over Garmin's 92-day limit are automatically chunked and responses stitched together.

Instructions

Get menstrual calendar data between specified dates

    Automatically chunks requests longer than 92 days, Garmin's
    server-side limit, and stitches the responses together.
    Identical records spanning a chunk boundary are returned once for list
    and dict-of-list responses. Other payload shapes are returned per chunk.
    
    Args:
        start_date: Start date in YYYY-MM-DD format
        end_date: End date in YYYY-MM-DD format
    

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_menstrual_calendar_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: automatic chunking above the 92-day server-side limit and cross-boundary deduplication of identical records for list and dict-of-list payloads, with other shapes returned per chunk. It still omits return-field details, timezone handling, and error behavior, keeping it short of a 5.

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?

The core purpose is front-loaded in the first line, followed by the chunking caveat and a compact Args block. The Args section partly repeats the schema, but the format detail earns its place given 0% schema coverage; no sentence is clearly wasteful.

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 two-parameter read tool with annotations covering safety and no output schema, the definition supplies the essential context an agent needs: date format, the server-side 92-day limit, automatic chunking, and deduplication semantics. Only minor details such as inclusive/exclusive date bounds and returned record shape are left unstated.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it does document both parameters with the required YYYY-MM-DD format that the schema's bare titles do not convey. It does not clarify whether end_date is inclusive or how boundaries interact with the 92-day chunking, leaving a small gap.

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 opens with a specific verb and resource ('Get menstrual calendar data') plus the scoping dimension ('between specified dates'), which distinguishes it from the sibling get_menstrual_data_for_date by implication of a range. It stops short of explicitly naming that single-date sibling, so the differentiation is inferable rather than stated.

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?

Usage is only implied by the date-range framing; there is no explicit statement of when to prefer this over get_menstrual_data_for_date or any other menstrual/calendar tool, and no exclusions or prerequisites. An agent can guess the intent, but the definition does not route it.

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