Skip to main content
Glama

BabyData pregnancy calculators

Ovulation calculator

calculate_ovulation
Read-onlyIdempotent

Estimate the likely ovulation day, the fertile window and the next period from the first day of the last period and the average cycle length. Informational only.

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": {
      "lastPeriod": "<lastPeriod>"
    },
    "name": "calculate_ovulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
lastPeriodYesFirst day of last period as YYYY-MM-DD.
cycleLengthNoAverage cycle length in days, 20 to 45 (default 28).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds one genuinely useful behavioral note — 'Informational only', signaling non-medical-advice framing — but says nothing about precision, variability of results, or how outputs are derived. With rich annotations, this modest addition merits a 3.

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?

Two compact sentences: the first front-loads the action, outputs, and inputs; the second carries the disclaimer. No redundant or filler wording.

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?

This is a simple, read-only, two-parameter calculation tool with a fully documented schema and annotations covering safety, so the description is nearly complete. It could be slightly stronger by noting the default cycle length or that results are estimates that vary with cycle regularity, but nothing essential for correct invocation is missing.

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 lastPeriod (YYYY-MM-DD) and cycleLength (20–45, default 28) fully documented in the schema. The description restates the parameter meanings in prose but adds no format, range, or edge-case detail beyond what the schema already provides, so baseline 3 applies.

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 uses a specific verb ('Estimate') and names all three outputs (ovulation day, fertile window, next period) plus the two inputs, so the tool's function is unmistakable. It does not explicitly contrast itself with siblings like calculate_due_date or pregnancy_weeks, so it stops short of a 5.

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?

Use context is implied by the purpose: an agent would know to call it for cycle/ovulation questions. However, there is no explicit when-to-use versus calculate_due_date or pregnancy_weeks, and no stated prerequisites beyond the input parameters. 'Informational only' hints at a scope limit but is not routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources