Skip to main content
Glama
tresor4k

macalc

calculate_pregnancy_due_date

Calculate your due date and current gestational week based on your last menstrual period. Get pregnancy timeline estimates instantly.

Instructions

Calculate due date and current gestational week from last period. Returns: {due_date}. See list_bundles for related 'sante' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
last_period_dateYesLast menstrual period date YYYY-MM-DD

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 provided, so description carries burden. It describes a pure computation with no side effects, but lacks details on edge cases (e.g., invalid dates, irregular cycles) and return format specifics beyond '{due_date}'.

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?

Description is extremely concise, two sentences with no extraneous information. Every word contributes to the purpose and provides a useful cross-reference.

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

Completeness3/5

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

For a simple calculation tool, the description covers key inputs and output. However, it fails to differentiate from the sibling 'calculate_due_date' and does not specify the due date format or gestational week output structure.

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 coverage is 100% with the parameter description already clear ('Last menstrual period date YYYY-MM-DD'). The description adds minor context ('from last period') but does not significantly enhance understanding beyond the schema.

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?

Description clearly states the tool calculates due date and current gestational week from last period, specifying the return field. Among many sibling calculators, this purpose is specific and unambiguous.

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 implies usage context (pregnancy calculation) and references 'list_bundles' for related calculators, but does not explicitly state when to use this tool over alternatives like 'calculate_due_date' or when not to use it.

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