DMD Costs legal costs tools

Employment tribunal time limit calculator (3 or 6 months; Acas early conciliation)

calculate_employment_tribunal_time_limit

Read-onlyIdempotent

Works out the last day to present an employment tribunal claim in England and Wales: 3 months less one day, or 6 months less one day where the relevant date is on or after 1 October 2026 (Employment Rights Act 2025 s.152 and Sch 12; S.I. 2026/954 reg 4; breach of contract by S.I. 2026/759), for unfair dismissal, discrimination, unlawful deductions, holiday pay, whistleblowing detriment, breach of contract, redundancy pay and equal pay, with Acas early conciliation (the clock-stop and the one-month rule) applied. Weekends and bank holidays do not move the date. It explains how a late claim can still be heard (not reasonably practicable, or just and equitable) but never predicts it, and never advises whether to claim.

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": {
      "claim": "<claim>",
      "start": "<start>"
    },
    "name": "calculate_employment_tribunal_time_limit"
  }
}

Input Schema

Name	Required	Description
`dayA`	No	Optional: Day A, the day Acas received the early conciliation notification.
`dayB`	No	Optional: Day B, the day the early conciliation certificate was received.
`claim`	Yes	The kind of claim.
`noEdt`	No	"contract": there is no effective date of termination, so start is the last day worked.
`start`	Yes	The day the time limit runs from: "unfair-dismissal": the effective date of termination; "discrimination": the date of the act complained of; "deductions": the date of payment of the wages; "holiday": the date the payment should have been made or the leave allowed; "detriment": the date of the act or failure to act; "contract": the effective date of termination; "redundancy": the relevant date; "equal-pay": the last day of the employment.
`ending`	No	"unfair-dismissal" (and where it matters): how the employment ended, for the effective date of termination: "notice" (With notice (worked, or on garden leave)), "summary" (Without notice, or with pay in lieu of notice), "fixed-term" (A fixed-term contract ended and was not renewed).
`presented`	No	Optional: the day the claim was or will be presented, to check it is in time.
`continuing`	No	"discrimination": conduct extending over a period (start is its end); "deductions" or "detriment": a series (start is the last in it).
`equalPayCase`	No	"equal-pay": the case in the EqA 2010 s.129(3) table: "standard" (A standard case), "stable" (A stable work case (a series of contracts)), "concealment" (A concealment case), "incapacity" (An incapacity case).
`interimRelief`	No	"unfair-dismissal": an application for interim relief is to be made (7 days, s.128(2)).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

changedInput schema / properties / dayA / description

Previous value: -"Optional: Day A, the day Acas received the early conciliation notification (YYYY-MM-DD)."New value: +"Optional: Day A, the day Acas received the early conciliation notification."

changedInput schema / properties / dayB / description

Previous value: -"Optional: Day B, the day the early conciliation certificate was received (YYYY-MM-DD)."New value: +"Optional: Day B, the day the early conciliation certificate was received."

changedInput schema / properties / presented / description

Previous value: -"Optional: the day the claim was or will be presented, to check it is in time (YYYY-MM-DD)."New value: +"Optional: the day the claim was or will be presented, to check it is in time."

changedInput schema / properties / start / description

Previous value: -"The day the time limit runs from: \"unfair-dismissal\": the effective date of termination; \"discrimination\": the date of the act complained of; \"deductions\": the date of payment of the wages; \"holiday\": the date the payment should have been made or the leave allowed; \"detriment\": the date of the act or failure to act; \"contract\": the effective date of termination; \"redundancy\": the relevant date; \"equal-pay\": the last day of the employment (YYYY-MM-DD)."New value: +"The day the time limit runs from: \"unfair-dismissal\": the effective date of termination; \"discrimination\": the date of the act complained of; \"deductions\": the date of payment of the wages; \"holiday\": the date the payment should have been made or the leave allowed; \"detriment\": the date of the act or failure to act; \"contract\": the effective date of termination; \"redundancy\": the relevant date; \"equal-pay\": the last day of the employment."

AddedOct 23, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description focuses on domain behavior: the 3-month vs 6-month rule keyed to 1 October 2026, clock-stop and one-month Acas rule, and that weekends/bank holidays do not move the date. Useful additions, though it never indicates the shape of the result (bare date vs date plus explanation of the EC extension).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is front-loaded in the first clause and there is no filler. However, the two sentences are heavily loaded with nested parentheticals and statutory citations (ERA 2025 s.152, S.I. 2026/954 reg 4, S.I. 2026/759) that make the operative rule harder to parse than it needs to be.

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 10-parameter tool with no output schema, the description covers scope, applicable law, the EC clock-stop behavior and its own limits. The remaining gap is the return value — whether it returns a date only, the extended date, or a pass/fail against the optional `presented` date — which an agent must infer.

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% and the per-parameter descriptions are already exhaustive (start-date semantics per claim, Day A/Day B, ending, continuing). The prose mentions Acas conciliation and the statutory bases, but adds no syntax or interaction detail beyond the schema, so the baseline 3 applies.

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 and resource — working out the last day to present an employment tribunal claim — and enumerates the claim types covered. It is clearly distinguishable from siblings like calculate_limitation_period and calculate_employment_tribunal_costs without needing to open 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context (England and Wales, eight enumerated claim types, Acas early conciliation applied) plus explicit scope exclusions: it 'never predicts' a late-claim outcome and 'never advises whether to claim'. It stops short of naming an alternative sibling (e.g. calculate_limitation_period) for non-ET limitation questions, so the when-not-to-use side is only partly covered.

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

All DMD Costs legal costs tools tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.