Due Date Calculator SkillDue Date Calculator Skill

OnlineCredit Usage:1 per callTool:DueDateCalculatorSkill

The tool

The API calculates current pregnancy progress, trimesters, important milestones, and time remaining until due date with week-by-week breakdowns.

Once your client is connected to the VerveKit MCP server, this appears in its tool list as DueDateCalculatorSkill. It is read-only and open-world: it fetches, it never mutates anything on your side, so most clients will call it without asking you to confirm.

Tool call
{
  "name": "DueDateCalculatorSkill",
  "arguments": {
    "last_period": "2025-06-01"
  }
}

What that looks like in a conversation

You don't name the tool — the model picks it. Asking about 2025-06-01 in the terms this source covers is enough for it to reach for DueDateCalculatorSkill on its own.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth — the client opens a browser once and there is no key to paste into a config file.

Client config
{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}
Endpoint
https://api.vervekit.com/v1/mcp

Per-client setup — Claude Desktop, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made.

ArgumentTypeExampleDescription
last_periodRequiredstring2025-06-01First day of last menstrual period (YYYY-MM-DD)

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client can read fields without parsing prose. status is "ok" on success and error is null; a null field means the value wasn't available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "calculation_method": "last_period",
    "last_period_date": "2024-01-01",
    "estimated_conception_date": "2024-01-15",
    "due_date": "2024-10-07",
    "current_progress": {
      "days_pregnant": 715,
      "weeks_pregnant": 102,
      "days_into_week": 1,
      "formatted": "102 weeks, 1 days",
      "trimester": 3,
      "percentage_complete": 255.36
    },
    "time_until_due": {
      "days": 0,
      "weeks": 0,
      "days_extra": 0,
      "formatted": "Past due date",
      "is_overdue": true
    },
    "upcoming_milestones": [],
    "important_dates": {
      "end_first_trimester": "2024-04-01",
      "end_second_trimester": "2024-07-08",
      "full_term_begins": "2024-09-16"
    },
    "disclaimer": "This is an estimate only. Due dates can vary. Consult your healthcare provider for medical advice."
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
calculation_methodstringlast_periodMethod used for calculation: last_period or conception_date
last_period_datePremiumstring2024-01-01Estimated first day of last menstrual period
estimated_conception_datePremiumstring2024-01-15Conception date provided as input
due_datestring2024-10-07Estimated delivery date in ISO format
current_progressobject{…}How far along the pregnancy is today, in days and weeks
current_progress.days_pregnantPremiumnumber715Total number of days pregnant
current_progress.weeks_pregnantPremiumnumber102Number of complete weeks of pregnancy
current_progress.days_into_weekPremiumnumber1Additional days beyond complete weeks
current_progress.formattedPremiumstring102 weeks, 1 daysHuman-readable pregnancy duration with weeks and days
current_progress.trimesterPremiumnumber3Current trimester number: 1, 2, or 3
current_progress.percentage_completePremiumnumber255.36Pregnancy completion percentage relative to due date
time_until_dueobject{…}How long until the due date, with a formatted summary
time_until_due.daysPremiumnumber0Complete days remaining until due date
time_until_due.weeksPremiumnumber0Complete weeks remaining until due date
time_until_due.days_extraPremiumnumber0Additional days beyond complete weeks remaining
time_until_due.formattedPremiumstringPast due dateHuman-readable time remaining until delivery
time_until_due.is_overduePremiumbooleantrueWhether pregnancy has passed the due date
upcoming_milestonesPremiumarray[]Array of upcoming pregnancy milestones and dates
important_datesobject{…}Key milestones: the end of each trimester and viability
important_dates.end_first_trimesterPremiumstring2024-04-01Estimated end date of first trimester
important_dates.end_second_trimesterPremiumstring2024-07-08Estimated end date of second trimester
important_dates.full_term_beginsPremiumstring2024-09-16Date when pregnancy reaches full term status
disclaimerstringThis is an estimate only. Due dates can vary. Consult your healthcare provider for medical advice.Medical disclaimer about estimated due dates

Failure modes

Errors come back as tool errors with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This skill isn't part of VerveKit. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Due Date Calculator Skill

Set up Due Date Calculator Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an X-API-Key header, with SDKs for Node, Python and .NET.APIVerveReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContextReference →

Frequently asked questions

Do I have to tell the agent to use DueDateCalculatorSkill?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveKit catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?