Skip to main content
Glama

DMD Costs legal costs tools

Fixed costs on issue, judgment and enforcement (CPR 45 Section II)

calculate_fixed_costs
Read-onlyIdempotent

Works out the fixed costs CPR 45 Section II allows a legal representative in England and Wales, line by line with the PD 45 table for each sum: fixed commencement costs on a money or goods claim (Table 2), judgment in default, on admission, summary judgment and Consumer Credit Act goods judgments (Table 3), possession and demotion claims (Tables 4 and 5), accelerated possession, extra service (Table 6) and enforcement (Table 7: charging orders, third party debt orders, writs, warrants, questioning, attachment of earnings). Online civil money claims follow PD 51R. No VAT and no London weighting; court fees are on top; the court can order otherwise. It never works out fixed recoverable costs (Part 45 Sections IV to X).

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": {
      "represented": "<represented>",
      "claim": "<claim>"
    },
    "name": "calculate_fixed_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
oprNo"possession": the claim is in the Online Procedure Rules digital service.
cjjaNoTable 7: registering a certificate under Schedule 6 to the Civil Jurisdiction and Judgments Act 1982.
stepNo"money" or "goods": where the claim has got to: "issue" (issued, nothing more yet), "paid" (the defendant paid in time, with the fixed costs), "default-ack" (default judgment, no acknowledgment of service), "default-defence" (default judgment, no defence), "admission-accepted" (judgment on admission, payment proposal accepted), "admission-court" (judgment on admission, the court decided payment), "summary" (summary judgment, or defence struck out, on application), "cca" (goods only: judgment for delivery under a Consumer Credit Act regulated agreement), "small-claims" (decided on the small claims track).
claimYesThe kind of claim: "money" (a claim for a specified sum of money), "goods" (a claim for delivery of goods), "possession" (possession of land, a demotion claim, or a Welsh prohibited conduct claim), "accelerated" (accelerated possession), "enforcement" (enforcement only), "unspecified" (unspecified damages), "hmrc" (a claim by an HMRC officer in the County Court).
routeNoHow it was issued (default paper): "paper" (on paper or Money Claim Online), "ocmc" (online civil money claims, PD 51R).
writsNoTable 7: writs of control or execution issued: a whole number, e.g. "1".
amountNo"money": the amount claimed on the claim form; "goods": the value of the goods stated, in pounds (e.g. "12500.50").
serviceNoHow the claim form was served: "court" (by the court, or otherwise), "personal" (personally, by the claimant).
judgmentNoThe judgment sum, if different from the amount claimed: debt and interest, without court fees and costs, in pounds (e.g. "12500.50").
landStepNo"possession": where the claim has got to: "issue" (issued), "gave-up" (possession given up, arrears paid), "judgment" (possession order made).
warrantsNoTable 7: requests for a warrant of control or delivery, for a sum over £25: a whole number, e.g. "1".
altServiceNoTable 6: service by an alternative method or at an alternative place (CPR 6.15), number of individuals served: a whole number, e.g. "1".
representedYesWhether the party claiming the costs has a solicitor or other legal representative: "yes", or "no" (acting in person).
landJudgmentNo"possession" with landStep "judgment": the kind of order: "arrears" (rent arrears claim with a fixed hearing date, not defended), "demotion" (a successful demotion or prohibited conduct claim), "other" (something else: defended, or on other grounds).
personalDocsNoTable 6: other documents required to be served personally, number of individuals served: a whole number, e.g. "1".
servedAbroadNoTable 6: services out of the jurisdiction anywhere else: a whole number, e.g. "1".
chargingOrderNoTable 7: a final charging order.
tpdoRecoveredNoTable 7: amount recovered under a final third party debt order, in pounds (e.g. "12500.50").
aoeAttendancesNoTable 7: attendances at an attachment of earnings hearing: a whole number, e.g. "1".
extraDefendantsNoFurther defendants personally served by the claimant at separate addresses: a whole number, e.g. "1".
awardOutstandingNoTable 7: the amount outstanding under an award enforced as if payable under a court order (CPR 70.5(4)), in pounds (e.g. "12500.50").
goodsValueStatedNo"goods": a value for the goods was stated on the claim form (default true).
servedScotlandEtcNoTable 6: services out of the jurisdiction in Scotland, Northern Ireland, the Isle of Man or the Channel Islands: a whole number, e.g. "1".
questioningMinutesNoTable 7: minutes of questioning a judgment debtor before a court officer: a whole number, e.g. "1".
acceleratedUndefendedNo"accelerated": a possession order was made and the defendant did not defend.
moneyInCourtRecoveredNoTable 7: amount recovered by payment out of money in court (CPR 72.10(1)(b)), in pounds (e.g. "12500.50").
noFixedCostsOnClaimFormNoThe claim form did not claim fixed commencement costs.
possessionPermissionPersonsNoTable 7: permission to enforce a possession order (CPR 83.13), persons given notice: a whole number, e.g. "1".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"\"money\": the amount claimed on the claim form; \"goods\": the value of the goods stated, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"\"money\": the amount claimed on the claim form; \"goods\": the value of the goods stated, in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / awardOutstanding / description
      Previous value: -"Table 7: the amount outstanding under an award enforced as if payable under a court order (CPR 70.5(4)), in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Table 7: the amount outstanding under an award enforced as if payable under a court order (CPR 70.5(4)), in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / judgment / description
      Previous value: -"The judgment sum, if different from the amount claimed: debt and interest, without court fees and costs, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"The judgment sum, if different from the amount claimed: debt and interest, without court fees and costs, in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / moneyInCourtRecovered / description
      Previous value: -"Table 7: amount recovered by payment out of money in court (CPR 72.10(1)(b)), in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Table 7: amount recovered by payment out of money in court (CPR 72.10(1)(b)), in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / tpdoRecovered / description
      Previous value: -"Table 7: amount recovered under a final third party debt order, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Table 7: amount recovered under a final third party debt order, in pounds (e.g. \"12500.50\")."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description instead adds substantive scope caveats: no VAT, no London weighting, court fees excluded, court may order otherwise, and that output is line-by-line per table. That last point is useful because there is no output schema, though it doesn't say how the result is formatted or which optional inputs override others.

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 core purpose and then densely enumerates tables and scope limits in roughly 110 words with no filler. It is a single undifferentiated block, which makes the exclusion/caveat sentences harder to scan, but little could be cut without losing coverage.

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 28-parameter, multi-table calculator with no output schema, the description covers scope, table coverage, exclusions and key caveats, which is enough for an agent to decide and call it. It stops short of explaining how the many optional parameters combine or which are relevant per claim type, leaving that to the enums.

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% and every one of the 28 parameters carries its own explanation with examples and table references, so the schema does the heavy lifting. The description adds only the table-to-parameter grouping (Tables 2–7), which is mild added value over what the schema already states — 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 precise verb and resource ('works out the fixed costs CPR 45 Section II allows') and enumerates exactly which PD 45 tables are covered. It also draws the negative boundary ('never works out fixed recoverable costs (Part 45 Sections IV to X)') and implicitly separates itself from calculate_civil_court_fees ('court fees are on top') and check_vat_on_costs ('No VAT').

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 clear context for when it applies (issue, default/admission/summary judgment, CCA goods, possession, enforcement, OCMC under PD 51R) and an explicit exclusion for FRC. It does not name a sibling as the alternative for the excluded FRC case, so routing is clear but not fully closed.

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