Skip to main content
Glama

Sync My Cycle

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

The days ahead by phase

get_week_ahead
Read-onlyIdempotent

The days ahead by phase. For when the user wants to plan training or meals for the week, for example "plan my training this week around my cycle". Returns each day's likely phase, workout focus, intensity and food focus. Not for getting pregnant, fertile days, ovulation timing, contraception or pregnancy: this is general wellbeing only, not for pregnancy planning or contraception, and it is not a fertility calendar. When period_may_be_late is true, days is empty and the say line suggests checking with a doctor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tzNoThe user's IANA time zone, for example Europe/London or America/Chicago, so today is the user's today. Optional: country is enough in most places.
dateNoFirst day of the plan, YYYY-MM-DD, a real calendar day. Default today where the user is: from tz, else country, else the request, else UTC.
daysNoHow many days, a whole number from 1 to 35. Default 7.
dietNoAccepted for symmetry with get_todays_phase; the week view has no food list, so it has no effect here.
countryNoTwo-letter country code (UK is read as GB), used for the time zone of today.
last_periodYesFirst day of the user's most recent period, YYYY-MM-DD. Must be within the last 120 days.
cycle_lengthNoUsual cycle length, 20 to 45. Default 28.
period_lengthNoUsual days of bleeding, 2 to 10. Default 5.
last_period_startNoOlder name for last_period, kept for existing callers; last_period is the current name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"Two-letter country code (UK is read as GB), used for the time zone of today. Pass it for users outside the US."New value: +"Two-letter country code (UK is read as GB), used for the time zone of today."
    • changedInput schema / properties / diet / description
      Previous value: -"Accepted for symmetry with /v1/today; the week view has no food list, so it has no effect here."New value: +"Accepted for symmetry with get_todays_phase; the week view has no food list, so it has no effect here."
    • changedInput schema / properties / last_period_start / description
      Previous value: -"Older name for last_period, kept for existing callers. Use last_period."New value: +"Older name for last_period, kept for existing callers; last_period is the current name."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine edge-case behavior beyond that: when `period_may_be_late` is true, `days` is empty and the say line advises a doctor. It does not cover pagination or precision caveats, but for a read-only tool this is solid added context.

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?

Front-loaded with purpose and trigger, which is good, but the exclusion sentence is bloated and self-repeating ('not for pregnancy planning or contraception... it is not a fertility calendar' after already listing pregnancy and contraception). Tighter phrasing would preserve the exclusions with less redundancy.

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?

With no output schema, the description carries the return-shape burden and does name the four returned fields plus the empty-result behavior. It is complete enough to call correctly; only minor gaps remain around how phase prediction degrades when cycle history is short.

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 100%, so every parameter, including the deprecated `last_period_start` alias and the no-op `diet`, is already documented in the schema. The description adds no parameter syntax or format detail beyond that, which is the correct baseline when the schema does the work.

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?

The description states a specific resource and scope (each day's likely phase, workout focus, intensity and food focus) and implicitly contrasts with get_todays_phase by being the multi-day view. An agent can distinguish it from siblings without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a concrete trigger ('plan training or meals for the week, for example "plan my training this week around my cycle"') plus an explicit exclusion list (pregnancy, fertile days, ovulation timing, contraception) and names the alternative domain. Nothing about when-not-to-use is left to inference.

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

All Sync My Cycle toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources