Skip to main content
Glama

DMD Costs legal costs tools

Part 35 questions to experts and Part 18 request dates

calculate_part_35_and_part_18_dates
Read-onlyIdempotent

Works out the dates for written questions to an expert (CPR 35.6: within 28 days of service of the report, deemed service under CPR 6.26, once only and for clarification unless the court permits or the other party agrees; before proceedings, the pre-action protocol that applies, of which only the Personal Injury Protocol fixes 28 days) and for a Part 18 request for further information (PD 18: the date for the response, and what can be done if none comes, including the application and its fee). On the small claims track CPR 27.2 disapplies both, and it says so. The page also builds a Word template; this tool gives the dates only and never drafts questions.

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": {
      "kind": "<kind>"
    },
    "name": "calculate_part_35_and_part_18_dates"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhat is being sent: "part35" (Written questions to an expert (Part 35)), "part18" (A Request for further information (Part 18)).
leaveNo"part35": permission or agreement for questions outside the rule: "" (Neither), "permission" (The court has given permission), "agreement" (The other party has agreed).
partyNoThe party putting the questions or making the request: "claimant" (the claimant), "defendant" (the defendant).
replyNo"part18": what has come back: "" (Not due yet, or not known), "none" (No response at all), "objection" (An objection, or a note that it cannot comply in time), "incomplete" (A response that does not answer the Request).
expertNo"part35": whose expert: "other-party" (The other side’s expert), "single-joint" (A single joint expert).
orderByNoOptional, "part18": the date an order under CPR 18.1 (or CPR 27.2(3)) gives for the response.
protocolNo"part35" before proceedings: the pre-action protocol: "" (Choose the protocol), "pi" (Personal Injury (not a whiplash report)), "disease" (Disease and Illness (including noise-induced hearing loss)), "housing" (Housing Conditions (England)), "clinical" (Resolution of Clinical Disputes), "other" (Another protocol, or none).
preActionNo"part35": before proceedings, when the pre-action protocols apply instead of CPR 35.6.
alreadyPutNo"part35": questions have already been put on this report (once only, CPR 35.6(2)(a)).
reportDateNo"part35": the date the report was served or, with reportMethod, sent.
reportLateNo"part35": the report was emailed, faxed or delivered at or after 4.30pm.
responseByNo"part18": the date the request gives for the response.
requestDateNo"part18": the date the request is made and sent.
requestLateNo"part18": the request is emailed or delivered at or after 4.30pm.
smallClaimsNoThe claim is on the small claims track (CPR 27.2 disapplies CPR 35.6 and Part 18).
reportMethodNo"part35": how the report was served, for deemed service under CPR 6.26: "" (I know the date of service), "email", "first-class-post", "document-exchange" (Document exchange (DX)), "delivery" (Delivered to the address), "fax", "personal" (Personal service).
questionsDateNoOptional, "part35": the day the questions are or were sent.
questionsLateNoOptional, "part35": the questions are emailed or delivered at or after 4.30pm.
requestMethodNo"part18": how the request is sent: "" (Another way: I will enter the date of service), "email", "first-class-post", "document-exchange" (Document exchange (DX)), "delivery" (Delivered to the address), "fax", "personal" (Personal service).
requestServedNo"part18" with no requestMethod: the day the request was served.
orderAnswersByNoOptional, "part35": the date the court's directions give for the answers.
questionsMethodNoOptional, "part35": how the questions are sent: "" (Not chosen yet), "email", "first-class-post", "document-exchange" (Document exchange (DX)), "delivery" (Delivered to the address), "fax", "personal" (Personal service).
orderQuestionsByNoOptional, "part35": the date the court's directions give for the questions.
beyondClarificationNo"part35": the questions go beyond clarifying the report (CPR 35.6(2)(c)).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / orderAnswersBy / description
      Previous value: -"Optional, \"part35\": the date the court's directions give for the answers (YYYY-MM-DD)."New value: +"Optional, \"part35\": the date the court's directions give for the answers."
    • changedInput schema / properties / orderBy / description
      Previous value: -"Optional, \"part18\": the date an order under CPR 18.1 (or CPR 27.2(3)) gives for the response (YYYY-MM-DD)."New value: +"Optional, \"part18\": the date an order under CPR 18.1 (or CPR 27.2(3)) gives for the response."
    • changedInput schema / properties / orderQuestionsBy / description
      Previous value: -"Optional, \"part35\": the date the court's directions give for the questions (YYYY-MM-DD)."New value: +"Optional, \"part35\": the date the court's directions give for the questions."
    • changedInput schema / properties / questionsDate / description
      Previous value: -"Optional, \"part35\": the day the questions are or were sent (YYYY-MM-DD)."New value: +"Optional, \"part35\": the day the questions are or were sent."
    • changedInput schema / properties / questionsMethod / description
      Previous value: -"Optional, \"part35\": how the questions are sent: \"\" (Not chosen yet), \"email\" (Email), \"first-class-post\" (First class post), \"document-exchange\" (Document exchange (DX)), \"delivery\" (Delivered to the address), \"fax\" (Fax), \"personal\" (Personal service)."New value: +"Optional, \"part35\": how the questions are sent: \"\" (Not chosen yet), \"email\", \"first-class-post\", \"document-exchange\" (Document exchange (DX)), \"delivery\" (Delivered to the address), \"fax\", \"personal\" (Personal service)."
    • changedInput schema / properties / reportDate / description
      Previous value: -"\"part35\": the date the report was served or, with reportMethod, sent (YYYY-MM-DD)."New value: +"\"part35\": the date the report was served or, with reportMethod, sent."
    • changedInput schema / properties / reportMethod / description
      Previous value: -"\"part35\": how the report was served, for deemed service under CPR 6.26: \"\" (I know the date of service), \"email\" (Email), \"first-class-post\" (First class post), \"document-exchange\" (Document exchange (DX)), \"delivery\" (Delivered to the address), \"fax\" (Fax), \"personal\" (Personal service)."New value: +"\"part35\": how the report was served, for deemed service under CPR 6.26: \"\" (I know the date of service), \"email\", \"first-class-post\", \"document-exchange\" (Document exchange (DX)), \"delivery\" (Delivered to the address), \"fax\", \"personal\" (Personal service)."
    • changedInput schema / properties / requestDate / description
      Previous value: -"\"part18\": the date the request is made and sent (YYYY-MM-DD)."New value: +"\"part18\": the date the request is made and sent."
    • changedInput schema / properties / requestMethod / description
      Previous value: -"\"part18\": how the request is sent: \"\" (Another way: I will enter the date of service), \"email\" (Email), \"first-class-post\" (First class post), \"document-exchange\" (Document exchange (DX)), \"delivery\" (Delivered to the address), \"fax\" (Fax), \"personal\" (Personal service)."New value: +"\"part18\": how the request is sent: \"\" (Another way: I will enter the date of service), \"email\", \"first-class-post\", \"document-exchange\" (Document exchange (DX)), \"delivery\" (Delivered to the address), \"fax\", \"personal\" (Personal service)."
    • changedInput schema / properties / requestServed / description
      Previous value: -"\"part18\" with no requestMethod: the day the request was served (YYYY-MM-DD)."New value: +"\"part18\" with no requestMethod: the day the request was served."
    • changedInput schema / properties / responseBy / description
      Previous value: -"\"part18\": the date the request gives for the response (YYYY-MM-DD)."New value: +"\"part18\": the date the request gives for the response."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavioral context beyond that: it says small claims disapplication is reported and that the tool never drafts questions, though it does not describe the return shape or error behavior.

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 purpose is front-loaded, and every sentence carries relevant legal information. However, the first sentence is very long with nested parentheticals and semicolons, making it denser and harder to parse than necessary for an agent-facing definition.

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 complex legal domain, rich schema, and annotations covering safety, the description is largely complete. It explains the two regimes, the small claims exception, and the no-drafting boundary; it need not explain return values because no output schema exists, though it could say more about how results are presented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all 24 parameters are already documented in the input schema. The description adds legal meaning that helps interpret several parameters, including CPR 35.6’s once-only/ clarification limits, deemed service, the pre-action protocol point that only the Personal Injury Protocol fixes 28 days, and small claims disapplication, but it does not spell out conditional dependencies among parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and two precise resources: calculating dates for Part 35 written questions to experts and Part 18 requests for further information. It cites the governing rules, so the agent can identify the tool’s niche, but it does not explicitly distinguish itself from sibling deadline calculators such as calculate_cpr_deadline or calculate_pre_action_protocol_deadlines.

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?

It gives clear usage context by explaining that CPR 27.2 disapplies both regimes on the small claims track and that the tool gives dates only and never drafts questions. That is a useful exclusion, but it does not name alternative sibling tools or state explicitly when to choose them over this one.

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