DMD Costs legal costs tools

Statutory demand deadline calculator (Insolvency Act 1986 ss.123 and 268; IR 2016)

calculate_statutory_demand_deadlines

Read-onlyIdempotent

Works out the statutory demand and petition timetable in England and Wales: on a company (Insolvency Act 1986 s.123(1)(a): 3 weeks to pay, secure or compound, then a winding-up petition) or on an individual (s.268: 18 days to apply to set the demand aside under IR 2016 r.10.4, 21 days to comply, then a bankruptcy petition for at least £5,000), with personal service and CPR 6.26, a set-aside application stopping the clock, the four-month rule, service of the petition (CPR 6.14), the Gazette notice, the certificate of compliance, notices of opposition and of intention to appear, and the court fee and official receiver's deposit. For a company, business days leave out Scotland's bank holidays too (s.251). Demands served abroad are not covered. Says where a date rests on a reading.

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": {
      "debtor": "<debtor>",
      "served": "<served>"
    },
    "name": "calculate_statutory_demand_deadlines"
  }
}

Input Schema

Name	Required	Description
`abroad`	No	"individual": the demand was served outside England and Wales (not covered: the periods differ, IR 2016 r.10.1(10)).
`amount`	No	The sum demanded (optional), for the £750 company and £5,000 bankruptcy thresholds, in pounds (e.g. "12500.50").
`debtor`	Yes	Who the demand is served on: "company" (a company: winding up), "individual" (an individual: bankruptcy).
`method`	No	"individual": how the demand was served (default personal): "personal" (handed to the debtor personally), "acknowledged" (service acknowledged in writing), "certificate" (another way (date in the certificate of service)).
`served`	Yes	"company": the day the demand was left at the registered office. "individual": the day it was served (see method).
`hearing`	No	The date of the hearing of the petition.
`setAside`	No	"individual": any application to set the demand aside: "" (no application, or not known), "pending" (applied, not yet decided), "dismissed-papers" (dismissed without a hearing), "dismissed-hearing" (dismissed at a hearing), "set-aside" (the demand was set aside).
`orderFrom`	No	Where setAside is "dismissed-hearing": the date in the order from which a petition may be presented, if it gives one.
`presented`	No	The date the petition was presented.
`servedTime`	No	"individual", served personally: the time it was handed over, for CPR 6.26 (24-hour HH:MM). Leave out if not known.
`setAsideFiled`	No	"individual": the date the application to set the demand aside was filed.
`petitionServed`	No	The day the petition was handed over ("individual") or served at the registered office ("company").
`setAsideDecided`	No	"individual": the date the application was dismissed, or the demand set aside.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 1, 2026

changedInput schema / properties / amount / description

Previous value: -"The sum demanded (optional), for the £750 company and £5,000 bankruptcy thresholds, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"The sum demanded (optional), for the £750 company and £5,000 bankruptcy thresholds, in pounds (e.g. \"12500.50\")."

changedInput schema / properties / hearing / description

Previous value: -"The date of the hearing of the petition (YYYY-MM-DD)."New value: +"The date of the hearing of the petition."

changedInput schema / properties / orderFrom / description

Previous value: -"Where setAside is \"dismissed-hearing\": the date in the order from which a petition may be presented, if it gives one (YYYY-MM-DD)."New value: +"Where setAside is \"dismissed-hearing\": the date in the order from which a petition may be presented, if it gives one."

changedInput schema / properties / petitionServed / description

Previous value: -"The day the petition was handed over (\"individual\") or served at the registered office (\"company\") (YYYY-MM-DD)."New value: +"The day the petition was handed over (\"individual\") or served at the registered office (\"company\")."

changedInput schema / properties / presented / description

Previous value: -"The date the petition was presented (YYYY-MM-DD)."New value: +"The date the petition was presented."

changedInput schema / properties / served / description

Previous value: -"\"company\": the day the demand was left at the registered office. \"individual\": the day it was served (see method) (YYYY-MM-DD)."New value: +"\"company\": the day the demand was left at the registered office. \"individual\": the day it was served (see method)."

changedInput schema / properties / setAsideDecided / description

Previous value: -"\"individual\": the date the application was dismissed, or the demand set aside (YYYY-MM-DD)."New value: +"\"individual\": the date the application was dismissed, or the demand set aside."

changedInput schema / properties / setAsideFiled / description

Previous value: -"\"individual\": the date the application to set the demand aside was filed (YYYY-MM-DD)."New value: +"\"individual\": the date the application to set the demand aside was filed."

AddedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/non-destructive, so the safety profile is covered. The description adds real behavioural context beyond that: the s.251 rule that company business days exclude Scotland's bank holidays, the four-month rule, and notably 'Says where a date rests on a reading', which tells the agent the output flags interpretive assumptions rather than presenting everything as certain.

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

Conciseness3/5

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

The core is front-loaded — the two timetable branches come first — but the whole definition is one sprawling run-on sentence with a long trailing 'and ... and ...' enumeration of peripheral items (Gazette notice, certificate of compliance, notices of opposition, court fee and OR deposit) that is hard to parse and buries the important abroad exclusion at the end.

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 13-parameter tool with no output schema, the description covers scope, thresholds, exclusions, day-counting quirks and the interpretive-flag behaviour well. The one real gap is that it never says what the tool returns (a dated timetable with warnings?), which matters because there is no output schema to fall back on.

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 every one of the 13 parameters (debtor, served, method, setAside, setAsideFiled, orderFrom, etc.) is already documented in the schema. The description reinforces a couple of them (the £5,000 bankruptcy threshold tied to `amount`, the company business-day rule) but adds no syntax or conditional-requirement detail the schema lacks. 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 (computes the statutory demand and petition timetable) and immediately scopes it to England and Wales with the exact statutory bases (s.123(1)(a) for companies, s.268 for individuals). This clearly separates it from generic siblings such as calculate_cpr_deadline and calculate_deemed_service, which cover different regimes.

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 a clear operating context (statutory demands against companies vs individuals, with the downstream petition) and one explicit exclusion: 'Demands served abroad are not covered.' It does not, however, name which sibling to use for the overlapping pieces (e.g. deemed service or CPR deadline calculation), so routing against alternatives is left to inference.

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.