Skip to main content
Glama

DMD Costs legal costs tools

Relief from sanctions, extensions of time and setting aside checker (CPR 3.9, 13.3, 47.12)

check_relief_from_sanctions
Read-onlyIdempotent

Works out which test applies when a deadline in a civil claim in England and Wales has been missed or is about to be, then lays out the questions the court asks, each with what the rule or the case says and your own answers: relief from sanctions under CPR 3.8 and 3.9 and the three Denton stages (late witness statements, budgets, experts' reports, disclosure, points of dispute, unless orders, late appeal notices); an extension applied for in time (Hallam Estates) or under CPR 3.1(2)(a); agreed extensions (CPR 2.11, 3.8(4), 15.5); the claim form (CPR 7.6); and setting aside a default judgment (CPR 13.2 and 13.3) or a default costs certificate (CPR 47.12). Says what to file, the N244 preset and the court fee. It never predicts the outcome or scores the answers: relief, extensions and setting aside are for the court.

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": {
      "track": "<track>"
    },
    "name": "check_relief_from_sanctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
paidNoDefault judgment: whether the whole claim, with any costs, had been paid before judgment.
stepNo"time": the step that needs more time: "defence" (the defence), "points-of-dispute", "sanction-step" (a step whose consequence is stated), "plain-step" (a step with no stated consequence), "court-dates" (hearing or trial dates), "claim-form" (serving the claim form).
trackYesWhat is needed: "relief" (relief from a sanction, or a step done late), "set-aside" (set aside a default judgment or a default costs certificate), "time" (more time for a step, by agreement or from the court).
agreedNo"time": whether the other side will agree.
breachNo"relief": what was missed: "unless-order" (an unless order), "witness" (late witness statement), "budget" (costs budget not filed), "expert" (expert's report not disclosed), "disclosure" (document not disclosed), "points-of-dispute" (late points of dispute), "other-express" (another rule or order stating the consequence), "appeal" (late appellant's notice), "respondent" (late respondent's notice), "particulars" (late particulars of claim), "unless-judgment" (judgment under CPR 3.5), "costs-order" (the sanction is a costs order), "no-sanction" (no stated consequence), "claim-form" (claim form not served in time).
inTimeNo"relief": whether the application is filed before the time for the step runs out.
reasonNoWhy the default happened: "illness" (illness of, or an accident to, the party or the solicitor), "later-developments" (later developments made the time allowed unreasonable), "overlooked" (the deadline was overlooked, or there was too much work), "unrepresented" (the party was acting in person and did not know the rules), "funds" (lack of funds to instruct lawyers), "other" (another reason), "none" (no explanation).
targetNo"set-aside": what is to be set aside: "default-judgment" (a default judgment, CPR Part 13), "dcc" (a default costs certificate, CPR 47.12).
appDateNoThe date of the application, made or planned.
dueDateNoThe deadline that was missed, or that applies.
expiredNo"time": whether the time for the step has already passed.
refusedNoWhether the other side refused to agree relief or a reasonable extension.
doneDateNoThe date the late step was done, if it has been.
evidenceNoWhether the evidence in support (a witness statement) is ready.
knewDateNoSetting aside: the date the defendant or paying party learned of the judgment or certificate, or could with reasonable diligence have learned enough to apply.
prospectNoDefault judgment: whether there is a defence with a real prospect of success.
remediedNo"relief": whether the step has now been done.
dccPapersNoDefault costs certificate: whether the bill, the certificate and draft points of dispute are ready to file.
defaultOfNoDefault judgment: entered in default of: "aos" (an acknowledgment of service), "defence" (a defence).
disruptedNo"relief": whether there was other disruption to this or other litigation.
podBeforeNoDefault costs certificate: whether points of dispute were served before it was issued.
filedFirstNoDefault judgment: whether the acknowledgment of service or defence had already been filed when judgment was entered.
goodReasonNoDefault costs certificate: whether there is a good reason for the detailed assessment to continue.
pendingAppNoDefault judgment: whether the defendant's application to strike out or for summary judgment was undecided.
hearingRiskNo"relief": whether a hearing date was lost or put at risk.
otherReasonNoDefault judgment: whether there is some other good reason to set it aside.
timeExpiredNoDefault judgment: whether the time for filing had expired when judgment was entered.
admittedTimeNoDefault judgment: whether the whole money claim had been admitted with a request for time to pay.
draftDefenceNoDefault judgment: whether a draft defence is ready to exhibit.
judgmentDateNoThe date of the judgment: for a default judgment the date entered; for a judgment under CPR 3.5 after an unless order, the date it was served on you.
pastBreachesNoWhether the party in default has other breaches.
hearingAtRiskNo"time" with "sanction-step": whether an extension would put a hearing date at risk.
podPeriodOverNoDefault costs certificate: whether the 21 days after service of the notice of commencement had expired when it was requested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed28 schema fields changed
    • changedInput schema / properties / admittedTime / description
      Previous value: -"Default judgment: whether the whole money claim had been admitted with a request for time to pay: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether the whole money claim had been admitted with a request for time to pay."
    • changedInput schema / properties / agreed / description
      Previous value: -"\"time\": whether the other side will agree: \"yes\", \"no\" or \"unsure\"."New value: +"\"time\": whether the other side will agree."
    • changedInput schema / properties / appDate / description
      Previous value: -"The date of the application, made or planned (YYYY-MM-DD)."New value: +"The date of the application, made or planned."
    • changedInput schema / properties / dccPapers / description
      Previous value: -"Default costs certificate: whether the bill, the certificate and draft points of dispute are ready to file: \"yes\" or \"no\"."New value: +"Default costs certificate: whether the bill, the certificate and draft points of dispute are ready to file."
    • changedInput schema / properties / disrupted / description
      Previous value: -"\"relief\": whether there was other disruption to this or other litigation: \"yes\", \"no\" or \"unsure\"."New value: +"\"relief\": whether there was other disruption to this or other litigation."
    • changedInput schema / properties / doneDate / description
      Previous value: -"The date the late step was done, if it has been (YYYY-MM-DD)."New value: +"The date the late step was done, if it has been."
    • changedInput schema / properties / draftDefence / description
      Previous value: -"Default judgment: whether a draft defence is ready to exhibit: \"yes\" or \"no\"."New value: +"Default judgment: whether a draft defence is ready to exhibit."
    • changedInput schema / properties / dueDate / description
      Previous value: -"The deadline that was missed, or that applies (YYYY-MM-DD)."New value: +"The deadline that was missed, or that applies."
    • changedInput schema / properties / evidence / description
      Previous value: -"Whether the evidence in support (a witness statement) is ready: \"yes\" or \"no\"."New value: +"Whether the evidence in support (a witness statement) is ready."
    • changedInput schema / properties / expired / description
      Previous value: -"\"time\": whether the time for the step has already passed: \"yes\" or \"no\"."New value: +"\"time\": whether the time for the step has already passed."
    • changedInput schema / properties / filedFirst / description
      Previous value: -"Default judgment: whether the acknowledgment of service or defence had already been filed when judgment was entered: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether the acknowledgment of service or defence had already been filed when judgment was entered."
    • changedInput schema / properties / goodReason / description
      Previous value: -"Default costs certificate: whether there is a good reason for the detailed assessment to continue: \"yes\", \"no\" or \"unsure\"."New value: +"Default costs certificate: whether there is a good reason for the detailed assessment to continue."
    • changedInput schema / properties / hearingAtRisk / description
      Previous value: -"\"time\" with \"sanction-step\": whether an extension would put a hearing date at risk: \"yes\", \"no\" or \"unsure\"."New value: +"\"time\" with \"sanction-step\": whether an extension would put a hearing date at risk."
    • changedInput schema / properties / hearingRisk / description
      Previous value: -"\"relief\": whether a hearing date was lost or put at risk: \"yes\", \"no\" or \"unsure\"."New value: +"\"relief\": whether a hearing date was lost or put at risk."
    • changedInput schema / properties / inTime / description
      Previous value: -"\"relief\": whether the application is filed before the time for the step runs out: \"yes\" or \"no\"."New value: +"\"relief\": whether the application is filed before the time for the step runs out."
    • changedInput schema / properties / judgmentDate / description
      Previous value: -"The date of the judgment: for a default judgment the date entered; for a judgment under CPR 3.5 after an unless order, the date it was served on you (YYYY-MM-DD)."New value: +"The date of the judgment: for a default judgment the date entered; for a judgment under CPR 3.5 after an unless order, the date it was served on you."
    • changedInput schema / properties / knewDate / description
      Previous value: -"Setting aside: the date the defendant or paying party learned of the judgment or certificate, or could with reasonable diligence have learned enough to apply (YYYY-MM-DD)."New value: +"Setting aside: the date the defendant or paying party learned of the judgment or certificate, or could with reasonable diligence have learned enough to apply."
    • changedInput schema / properties / otherReason / description
      Previous value: -"Default judgment: whether there is some other good reason to set it aside: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether there is some other good reason to set it aside."
    • changedInput schema / properties / paid / description
      Previous value: -"Default judgment: whether the whole claim, with any costs, had been paid before judgment: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether the whole claim, with any costs, had been paid before judgment."
    • changedInput schema / properties / pastBreaches / description
      Previous value: -"Whether the party in default has other breaches: \"yes\", \"no\" or \"unsure\"."New value: +"Whether the party in default has other breaches."
    • changedInput schema / properties / pendingApp / description
      Previous value: -"Default judgment: whether the defendant's application to strike out or for summary judgment was undecided: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether the defendant's application to strike out or for summary judgment was undecided."
    • changedInput schema / properties / podBefore / description
      Previous value: -"Default costs certificate: whether points of dispute were served before it was issued: \"yes\", \"no\" or \"unsure\"."New value: +"Default costs certificate: whether points of dispute were served before it was issued."
    • changedInput schema / properties / podPeriodOver / description
      Previous value: -"Default costs certificate: whether the 21 days after service of the notice of commencement had expired when it was requested: \"yes\", \"no\" or \"unsure\"."New value: +"Default costs certificate: whether the 21 days after service of the notice of commencement had expired when it was requested."
    • changedInput schema / properties / prospect / description
      Previous value: -"Default judgment: whether there is a defence with a real prospect of success: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether there is a defence with a real prospect of success."
    • changedInput schema / properties / refused / description
      Previous value: -"Whether the other side refused to agree relief or a reasonable extension: \"yes\", \"no\" or \"unsure\"."New value: +"Whether the other side refused to agree relief or a reasonable extension."
    • changedInput schema / properties / remedied / description
      Previous value: -"\"relief\": whether the step has now been done: \"yes\", \"no\" or \"unsure\"."New value: +"\"relief\": whether the step has now been done."
    • changedInput schema / properties / step / description
      Previous value: -"\"time\": the step that needs more time: \"defence\" (the defence), \"points-of-dispute\" (points of dispute), \"sanction-step\" (a step whose consequence is stated), \"plain-step\" (a step with no stated consequence), \"court-dates\" (hearing or trial dates), \"claim-form\" (serving the claim form)."New value: +"\"time\": the step that needs more time: \"defence\" (the defence), \"points-of-dispute\", \"sanction-step\" (a step whose consequence is stated), \"plain-step\" (a step with no stated consequence), \"court-dates\" (hearing or trial dates), \"claim-form\" (serving the claim form)."
    • changedInput schema / properties / timeExpired / description
      Previous value: -"Default judgment: whether the time for filing had expired when judgment was entered: \"yes\", \"no\" or \"unsure\"."New value: +"Default judgment: whether the time for filing had expired when judgment was entered."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only safety and idempotence, but the description adds meaningful context: it outputs filing requirements, the N244 preset and court fee, and explicitly 'never predicts the outcome or scores the answers' because relief is for the court. That is a useful behavioural boundary not captured by annotations.

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?

Front-loaded with the purpose and then systematically enumerates routes; every clause carries substantive rule information. It is dense and long-winded in places, but the length is proportionate to the 33-parameter scope and no sentence is pure filler.

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?

Given the complexity (33 params, no output schema, 100% schema coverage), the description covers the full decision space and tells the agent what the output contains (questions plus rule/case answers, filing steps, fee). It does not explain how the required 'track' gates optional parameters, but that gating is visible in the schema.

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% across all 33 parameters, so the schema carries parameter semantics. The description adds no parameter-level detail beyond implying that answers feed into the laid-out questions; 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+resource: works out which test applies when a civil deadline is missed, then lays out the questions the court asks across CPR 3.9, 13.3 and 47.12. The enumerated sub-scenarios (Denton stages, Hallam Estates extensions, default judgment set-aside) make it clearly distinguishable from siblings like calculate_cpr_deadline.

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?

Explicitly frames the triggering condition—a deadline missed or about to be, or a default judgment/costs certificate to set aside—and lists the covered routes. It does not name specific alternatives or exclusions (e.g., when to use calculate_cpr_deadline instead), so it falls short of a 5.

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