Skip to main content
Glama

BabyData pregnancy calculators

Due date calculator

calculate_due_date
Read-onlyIdempotent

Estimate a pregnancy due date and current stage using Naegele's rule, from the last menstrual period (LMP), conception date, or an IVF embryo-transfer date. Returns the estimated due date, weeks pregnant now, trimester and weeks remaining. Informational only, not medical advice.

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": "calculate_due_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfNoReference date YYYY-MM-DD for "weeks pregnant now" (default today).
dateYesThe relevant date as YYYY-MM-DD: LMP, conception, or IVF transfer date.
methodNoDating method (default lmp).
embryoAgeNoEmbryo age in days at IVF transfer (commonly 3 or 5; default 5).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value beyond that by naming the computation rule, listing exactly what is returned (due date, weeks pregnant, trimester, weeks remaining), and adding the 'informational only, not medical advice' disclaimer. It does not describe error behavior for implausible dates, which keeps it from a 5.

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 front-loaded sentences plus a short disclaimer; the purpose and inputs come first, the return values second, and nothing is repeated or padded. Every clause carries information an agent would otherwise have to infer.

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 correctly compensates by enumerating the returned fields, and it covers all three dating methods. It is nearly complete for a simple calculator; the only gap is that it does not say what happens with future or implausible dates or how the returned stage is derived relative to asOf.

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 the schema already explains date, method, asOf, and embryoAge including defaults and formats. The description's mention of LMP/conception/IVF transfer mirrors the method enum rather than adding new meaning. Baseline 3 applies since the schema carries the parameter burden.

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 names a specific verb and resource ('Estimate a pregnancy due date') plus the algorithm (Naegele's rule) and the three accepted dating inputs, so the tool's function is unmistakable. It does not, however, differentiate itself from the sibling 'pregnancy_weeks' even though it also returns 'weeks pregnant now', leaving a potential overlap for the agent to resolve on its own.

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?

Enumerating LMP, conception, and IVF transfer implies which dating scenario each input serves, which is useful context. But there is no explicit when-to-use guidance versus calculate_ovulation or pregnancy_weeks, no statement of when this tool should NOT be used, and no note on invalid or out-of-range dates.

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