Skip to main content
Glama

BabyData pregnancy calculators

UK maternity pay calculator

maternity_pay
Read-onlyIdempotent

Estimate UK Statutory Maternity Pay over the 39 weeks under gov.uk rules: 90% of average weekly earnings for 6 weeks, then the lower of the statutory flat rate or 90%. Uses the 2026-27 gov.uk flat rate of £194.32 a week, which changes each April. Estimate only, not advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "maternity_pay"
  }
}

Input Schema

NameRequiredDescriptionDefault
annualSalaryNoAnnual salary before tax (GBP), converted at /52.
weeklyEarningsNoAverage weekly earnings before tax (GBP).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the description's job is lighter. It adds genuinely useful context beyond that: the 6-week 90% phase, the subsequent lower-of comparison, the pinning to the 2026-27 flat rate of £194.32, and the fact that the rate resets each April. It stops short of describing the output shape or whether both earnings inputs are combined or one overrides the other.

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 tight sentences with the calculation logic front-loaded and the caveats trailing. Every clause carries information: formula, rate, versioning risk, and the advice disclaimer.

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?

For a deterministic two-parameter calculator whose safety profile is fully covered by annotations, this is nearly complete. The remaining gap is that no output schema exists and the description does not indicate what the estimate returns or how overlapping inputs are resolved.

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 both parameters are already documented, making 3 the baseline. The description adds no meaning about the relationship between annualSalary and weeklyEarnings — notably which one wins if both are supplied — so it does not exceed what the schema already provides.

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?

States a specific verb (Estimate) and resource (UK Statutory Maternity Pay over 39 weeks) plus the exact gov.uk rule structure. This is clearly distinct from the sibling date/gestation calculators, so an agent can select it without opening the schema.

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 (estimating SMP) and adds a boundary disclaimer ('Estimate only, not advice'), but never says when to prefer this over the sibling tools or what eligibility assumptions apply. It also gives no guidance on choosing between annualSalary and weeklyEarnings, leaving selection to inference.

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