Skip to main content
Glama
tresor4k

macalc

calculate_ovulation

Calculate your ovulation date and fertile window by entering your last menstrual period and cycle length. Get precise dates for ovulation, fertile window, and next period.

Instructions

Calculate ovulation date and fertile window from last period and cycle length. Returns: {lmp, ovulation_date, fertile_window_start, fertile_window_end, next_period}. See list_bundles for related 'sante' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
last_period_dateYesYYYY-MM-DD — First day of last menstrual period
cycle_lengthNoMenstrual cycle length in days

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does not mention whether the tool is read-only, stateless, or has any side effects. For a calculator, the behavior is implied but not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences that state purpose, list return fields, and reference related calculators. Every word is functional with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (two parameters, clear output schema referenced in description) and sibling context, the description provides all necessary information for an agent to use it correctly.

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% with both parameters described. The description adds minimal value beyond the schema, essentially restating the inputs without additional semantics.

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 clearly states the tool calculates 'ovulation date and fertile window' from specific inputs, listing the exact return fields. This distinguishes it from sibling calculators like calculate_menstrual_cycle by specifying the output structure.

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?

The description mentions inputs 'from last period and cycle length' but does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. The reference to list_bundles is vague.

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/tresor4k/macalc-mcp'

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