DMD Costs legal costs tools

Detailed assessment deadline calculator (CPR Part 47)

calculate_detailed_assessment_deadlines

Read-onlyIdempotent

Works out the CPR Part 47 detailed assessment timetable in England and Wales from the dates you have: the last day to serve the notice of commencement (N252), Points of Dispute, the first day for a default costs certificate (N254), Replies, the request for an assessment hearing (N258), provisional assessment steps and payment. Allows for deemed service, weekends, bank holidays and court office closures. Give at least the right to costs (its kind and date).

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": {
      "rightToCostsKind": "<rightToCostsKind>",
      "rightToCostsDate": "<rightToCostsDate>"
    },
    "name": "calculate_detailed_assessment_deadlines"
  }
}

Input Schema

Name	Required	Description
`hearingDate`	No	The date of the detailed assessment hearing, if one is listed.
`hearingEnded`	No	The date the detailed assessment hearing ended, if it has.
`noticeServed`	No	The date the notice of commencement was served (deemed service), if it has been.
`pointsServed`	No	The date Points of Dispute were served, if they have been.
`certificateDate`	No	The date of the final or interim costs certificate, if issued.
`rightToCostsDate`	Yes	The date of that judgment, order or event.
`rightToCostsKind`	Yes	What gave the right to costs: "judgment" (Judgment or order), "stay-lifted" (Stay lifted after appeal), "discontinuance-served", "discontinuance-upheld", "part-36-accepted" (Part 36 offer accepted).
`provisionalReceived`	No	The date the provisional assessment was received, if there was one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 1, 2026

changedInput schema / properties / certificateDate / description

Previous value: -"The date of the final or interim costs certificate, if issued (YYYY-MM-DD)."New value: +"The date of the final or interim costs certificate, if issued."

changedInput schema / properties / hearingDate / description

Previous value: -"The date of the detailed assessment hearing, if one is listed (YYYY-MM-DD)."New value: +"The date of the detailed assessment hearing, if one is listed."

changedInput schema / properties / hearingEnded / description

Previous value: -"The date the detailed assessment hearing ended, if it has (YYYY-MM-DD)."New value: +"The date the detailed assessment hearing ended, if it has."

changedInput schema / properties / noticeServed / description

Previous value: -"The date the notice of commencement was served (deemed service), if it has been (YYYY-MM-DD)."New value: +"The date the notice of commencement was served (deemed service), if it has been."

changedInput schema / properties / pointsServed / description

Previous value: -"The date Points of Dispute were served, if they have been (YYYY-MM-DD)."New value: +"The date Points of Dispute were served, if they have been."

changedInput schema / properties / provisionalReceived / description

Previous value: -"The date the provisional assessment was received, if there was one (YYYY-MM-DD)."New value: +"The date the provisional assessment was received, if there was one."

changedInput schema / properties / rightToCostsDate / description

Previous value: -"The date of that judgment, order or event (YYYY-MM-DD)."New value: +"The date of that judgment, order or event."

changedInput schema / properties / rightToCostsKind / description

Previous value: -"What gave the right to costs: \"judgment\" (Judgment or order), \"stay-lifted\" (Stay lifted after appeal), \"discontinuance-served\" (Discontinuance served), \"discontinuance-upheld\" (Discontinuance upheld), \"part-36-accepted\" (Part 36 offer accepted)."New value: +"What gave the right to costs: \"judgment\" (Judgment or order), \"stay-lifted\" (Stay lifted after appeal), \"discontinuance-served\", \"discontinuance-upheld\", \"part-36-accepted\" (Part 36 offer accepted)."

First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the bar is lower; the description still adds real value by disclosing the calculation rules applied (deemed service, weekends, bank holidays, court office closures) and the England-and-Wales jurisdiction. It does not describe the shape of the result, which matters given there is no output schema.

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?

Three front-loaded sentences that each do work: the first states the computation, the second the calendaring logic, the third the minimum inputs. The long deadline enumeration is information-dense rather than padded, though it could be trimmed.

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 read-only calculator with an 8-param fully documented schema and no output schema, the description covers purpose, jurisdiction, calculation rules and required inputs. The remaining gap is that an agent cannot tell what the response looks like (a list of labelled dates?) — the enumeration of deadlines partly compensates.

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% with an explained enum, so the schema carries the parameter burden and baseline 3 applies. The description adds only that the right-to-costs kind and date are mandatory minima; it does not explain how the optional dates interact (e.g. that supplying pointsServed shifts later deadlines).

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?

Names a specific computation ('works out the CPR Part 47 detailed assessment timetable') and enumerates the concrete deadlines produced (N252, Points of Dispute, N254, Replies, N258, provisional assessment, payment). This makes it clearly distinguishable from the generic sibling calculate_cpr_deadline and from calculate_deemed_service.

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?

"From the dates you have" plus "Give at least the right to costs (its kind and date)" tells the agent that partial inputs are acceptable and which two fields are the floor. It does not name an alternative tool or a when-not condition, so it stops short of full routing guidance.

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.