Skip to main content
Glama
davidmosiah

Wellness Cycle Coach

Cycle estimate phase

cycle_estimate_phase

Analyze period start dates to estimate current phase, cycle day, next period, and confidence. Supports irregular cycles with low confidence and late-luteal warnings.

Instructions

Given a list of recent period start dates (from any source), returns the current phase, cycle day, estimated cycle length, next-period date, and confidence. v0.3.2 adds a late_luteal sub-phase (triggered when the cycle is past its expected end + grace day) plus days_past_due and delay_flag (raised when ≥2 days late vs prediction from 3+ historical cycles). v0.3.3 adds cycle_irregular (PCOS / irregular-cycle mode): when true, accepts cycles 21-90 days, caps confidence at 'low', returns luteal_extended + irregular_window: true past 35 days since last period, and adds a clinician-defer warning.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
todayNoOptional reference date; defaults to system today.
historyYesArray of {start_date: 'YYYY-MM-DD', length_days?: number}. Sorted automatically.
cycle_irregularNov0.3.3 — PCOS / irregular-cycle mode. When true: accepts cycles 21-90 days, caps confidence at 'low', returns `luteal_extended` when days_since_last > 35, and adds a clinician-defer warning string. Default false.
Behavior4/5

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

Despite no annotations, the description discloses key behaviors: version-specific sub-phases (late_luteal), irregular-cycle mode (cycle_irregular), confidence caps, and warning strings. This provides good context for safe invocation.

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 informative but includes detailed version history (v0.3.2, v0.3.3) that could be a changelog. It front-loads the core purpose, but the extra sentences reduce conciseness for an agent.

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?

Without an output schema, the description lists return fields (phase, cycle day, estimated length, next period, confidence) and flags (days_past_due, delay_flag, luteal_extended, irregular_window). It covers the needed context for agent decision-making.

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 coverage is 100%, with descriptions for all parameters (today, history, cycle_irregular). The description adds version-specific meaning, especially for cycle_irregular (PCOS mode, confidence caps, irregular_window).

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 states the function: given a list of recent period start dates, it returns phase, cycle day, estimated length, next period, and confidence. While it does not explicitly distinguish from siblings like cycle_predict_next_period or cycle_phase_guidance, the purpose is specific and actionable.

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?

No guidance on when to use this tool versus alternatives. The description focuses on version features and output details but does not mention context for selection, prerequisites, or when-not-to-use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/wellness-cycle-coach'

If you have feedback or need assistance with the MCP directory API, please join our Discord server