Skip to main content
Glama

DMD Costs legal costs tools

Calderbank offer letter builder (without prejudice save as to costs)

build_calderbank_offer
Read-onlyIdempotent

Drafts a written offer to settle a CLAIM marked "without prejudice save as to costs" (a Calderbank offer), in England and Wales, in the user's own terms: civil claims (issued or not), small claims, family proceedings outside FPR 28.3 (Schedule 1 claims, most interim applications other than interim variation) and employment tribunals; from a firm for its client or from the party itself; to the other side's solicitors or the other party. The costs term follows the offer's scope and pays Part 45 fixed costs where Part 45 fixes them (CPR 45.1(3)); a timed offer says a rejection or counter-offer will not end it, and a deadline on a weekend or bank holiday moves to the next working day; tribunal offers say the settlement will be recorded in a COT3 or settlement agreement (ERA 1996 s.203). Returns the letter text, the checks, the date the offer is open until, and what the court or tribunal can do with it: in civil claims the court has regard to an admissible offer that is not a Part 36 offer when deciding costs (CPR 44.2(4)(c)), nothing is automatic (CPR 36.2(2)) and Part 36's "by any amount, however small" test is not read into Part 44 (Coward v Phaestos Ltd [2014] EWCA Civ 1256); Part 36 does not apply once a claim is allocated to the small claims track (CPR 27.2(1)(g)); in employment tribunals rejection must be unreasonable (Sud v Ealing LBC [2013] EWCA Civ 949). It refuses financial remedy proceedings, including variation and interim variation (FPR 28.3(8)), and never drafts offers on costs (bills, detailed assessment), never puts a figure on costs and never suggests what to offer.

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": {
      "forum": "<forum>"
    },
    "name": "build_calderbank_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe letter's date (defaults to today).
sideNoWhich side makes the offer: "claiming" (the party bringing the claim), "responding" (the party defending it).
costsNoHow costs are dealt with if the offer is accepted: "pay" (the responding party pays the claiming party's costs of what the offer settles up to acceptance: in civil claims the Part 45 fixed costs where Part 45 fixes them, otherwise reasonable costs assessed on the standard basis if not agreed (civil and family only)), "own" (each party bears its own costs (the only choice in employment tribunals)), "reserved" (the costs of the part or issue settled are left to the court, with the costs of the rest (civil and family, part or issue offers only)), "fees" (the court fees the claimant has paid (small claims: issued, whole-claim offers only)).
courtNoThe court or tribunal (optional)
forumYesWhere the dispute is (financial remedy proceedings and disputes about costs are refused, with the reason): "civil" (A civil claim (fast, intermediate or multi-track, or not yet allocated)), "small-claims" (A small claim (allocated, or likely to be allocated, to the small claims track)), "family-other" (Family: a Schedule 1 claim, or an interim financial application other than an interim variation order), "employment" (An employment tribunal claim), "family-financial" (Family: financial remedy proceedings (divorce, dissolution, variation and interim variation)), "costs" (A dispute about costs (a bill, detailed assessment, costs-only)).
scopeNoWhat the offer settles (default whole): "whole" (the whole claim), "part" (part of the claim), "issue" (one issue).
stageNoWhether proceedings have been issued (default issued): "issued" (proceedings issued), "pre-action" (not yet issued).
termsNoOther terms, one per item, in the user's own words (at most 8, each up to 600 characters). In a query string, repeat terms= for each term or send a JSON array: commas inside a term are kept.
voiceNoWho signs the letter (default firm): "firm" (a firm writing for its client), "self" (the party itself).
amountNoThe sum offered: to pay (responding) or to accept (claiming); leave out for an offer on other terms only, in pounds (e.g. "12500.50").
ourRefNoOur reference (optional)
payDaysNoDays after acceptance for payment (default 14)
yourRefNoYour reference (optional)
interestNoInterest (default inclusive): "inclusive" (inclusive of interest), "plus" (plus a stated sum of interest).
openDaysNoDays the offer is open from the letter's date (default 21; "" for no time limit)
recipientNoWho receives it (default solicitors): "solicitors" (the other side's solicitors), "party" (the other party in person).
scopeTextNoFor part or issue: which, in the user's own words
claimNumberNoThe claim or case number
offereeFirmNoWhere recipient is solicitors: the other side's solicitors
offereeNameNoThe name of the other party (a company or public body is addressed "Dear Sir or Madam")
offerorFirmNoWhere voice is firm: the firm sending the letter
offerorNameNoThe name of the party making the offer
counterclaimNoAny counterclaim (default none): "none" (no counterclaim), "includes" (the offer settles it too), "excludes" (the counterclaim continues).
interestAmountNoWhere interest is "plus": the interest sum, in pounds (e.g. "12500.50").
protectedPartyNoCivil claims and small claims: a party to the claim is a child or protected party, so any settlement needs the court's approval (CPR 21.10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"The sum offered: to pay (responding) or to accept (claiming); leave out for an offer on other terms only, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"The sum offered: to pay (responding) or to accept (claiming); leave out for an offer on other terms only, in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / date / description
      Previous value: -"The letter's date (defaults to today) (YYYY-MM-DD)."New value: +"The letter's date (defaults to today)."
    • changedInput schema / properties / interestAmount / description
      Previous value: -"Where interest is \"plus\": the interest sum, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Where interest is \"plus\": the interest sum, in pounds (e.g. \"12500.50\")."
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial behavioural detail: what it refuses and why, that it never puts a figure on costs and never suggests what to offer, that a weekend/bank-holiday deadline rolls forward, that timed offers survive rejection, and what the resulting offer's costs consequences are before the court or tribunal.

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 clause is content-bearing, but the whole definition is one very long sentence chain dense with case citations and statutory cross-references. It is accurate yet hard to scan, and some authority citations (e.g. Coward, Sud) are more than an agent needs for tool selection.

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 25-parameter drafting tool with no output schema, the description does the necessary work of describing the return ("the letter text, the checks, the date the offer is open until, and what the court or tribunal can do with it") and the refusal paths. The gap is the absence of guidance on how the many optional parameters interact, though the schema largely covers that.

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 9 enums, so nearly all parameter meaning is already in the schema. The description adds only the general framing that terms are "in the user's own terms" and echoes the costs/Part 45 linkage; it supplies no per-parameter syntax or interaction rules beyond what the schema states.

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 artifact ("Drafts a written offer to settle... a Calderbank offer") and enumerates the exact fora covered. It also draws the line against the nearest sibling concept, Part 36, by citing CPR 36.2(2) and Coward v Phaestos, so an agent can tell this apart from calculate_part_36_offer.

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 lists when it applies (civil issued or not, small claims, family outside FPR 28.3, employment tribunals) and when it does not (financial remedy proceedings including variation/interim variation; disputes about costs, bills, detailed assessment). It does not name a sibling tool to use instead for the refused cases, so it falls short of a full 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