Skip to main content
Glama

get_menstrual_data_for_date

Read-only

Retrieve menstrual data for a specific date to review cycle, flow, or symptom details stored in Garmin Connect.

Instructions

Get menstrual data for a specific date

    Args:
        date: 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": {
      "date": "<date>"
    },
    "name": "get_menstrual_data_for_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/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 structurally. Beyond that the description adds nothing: no statement of what is returned when no record exists for the date, whether the date is interpreted in local time or UTC, or what data fields to expect.

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?

Very short and front-loaded: the purpose sentence comes first, followed by the one argument. The 'Args:' block is somewhat boilerplate for a single parameter but costs little space and is not misleading.

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?

For a simple single-parameter read tool with safety annotations present, the definition covers the essentials. With no output schema, however, the agent has no picture of the return shape or empty-result behavior, which the description could have supplied in one sentence.

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 description coverage is 0%, so the description must carry parameter meaning, and it does supply the required YYYY-MM-DD format that the bare 'string' schema lacks. It stops short of clarifying timezone, whether future dates are valid, or what happens for dates with no logged data.

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 states a specific verb and resource (get menstrual data) and scopes it to a single date, so an agent can tell what it retrieves. It does not, however, distinguish itself from the sibling get_menstrual_calendar_data, leaving the boundary between single-date and calendar retrieval unstated.

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?

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no named alternative despite a plausibly overlapping sibling (get_menstrual_calendar_data). The only usable cue is the implicit 'specific date' scoping in the name and one-line description.

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