Skip to main content
Glama

DMD Costs legal costs tools

Court of Protection deputy fixed costs calculator (PD 19B)

calculate_court_of_protection_fixed_costs
Read-onlyIdempotent

Works out the fixed costs a professional or public authority deputy may take from P's estate under Court of Protection Practice Direction 19B (the 2024 version, and the December 2017 version for periods ending before 1 April 2024), fee by fee: the deputy application, the annual management fees for property and affairs (the net-assets percentage below £20,300) and health and welfare, reports to the OPG, tax returns, trustee and PD 9D applications, property management, conveyancing and travel, with part years and VAT. Where the deputy takes detailed assessment instead, it gives the SCCO fee, the 75% cap on payments on account and the time limit, never an estimate of what an assessment would allow. Every figure is a maximum. DMD Costs does not act in Court of Protection matters.

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": {
      "deputy": "<deputy>",
      "order": "<order>"
    },
    "name": "calculate_court_of_protection_fixed_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
wipNoAssessment: work in progress for the management year (your figure), in pounds (e.g. "12500.50").
electNoWhere order is "assessment": "assessment" (take it, as the order provides) or "fixed" (elect fixed costs instead, para 5).
filedNoAssessment: the date the request (Form N258B) is filed, for the court fee.
itemsNoThe fees to work out, one entry each (up to 20).
orderYesWhat the order provides for the deputy's costs: "fixed" (fixed costs), "assessment" (detailed assessment by the SCCO), "inter-partes" (costs paid by another party, not out of P's estate).
deputyYesWho the deputy is: "solicitor" (a solicitor, an SRA-regulated trust corporation or a chartered legal executive), "other-solicitor-rates" (another professional deputy whose order authorises solicitors' rates), "public-authority" (an office holder of a public authority), "other-pa-rates" (another professional deputy on public authority rates, or whose order says fixed costs without saying which), "lay" (a lay deputy, such as a family member).
estimateNoAssessment: the estimate given to the OPG (your figure), in pounds (e.g. "12500.50").
notForProfitNo"other-pa-rates": a not-for-profit deputy, for the fixed travel rate.
vatRegisteredNoA deputy who is not a solicitor or a public authority is VAT registered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / estimate / description
      Previous value: -"Assessment: the estimate given to the OPG (your figure), in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Assessment: the estimate given to the OPG (your figure), in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / filed / description
      Previous value: -"Assessment: the date the request (Form N258B) is filed, for the court fee (YYYY-MM-DD)."New value: +"Assessment: the date the request (Form N258B) is filed, for the court fee."
    • changedInput schema / properties / items / items / properties / assets / description
      Previous value: -"Annual fees: P's total assets on the anniversary (or at the end of a part year), including P's home, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Annual fees: P's total assets on the anniversary (or at the end of a part year), including P's home, in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / items / items / properties / consideration / description
      Previous value: -"Conveyancing under the 2017 text: the price, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Conveyancing under the 2017 text: the price, in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / items / items / properties / date / description
      Previous value: -"The date for the fee: the order date (application), the anniversary (annual fees), the date lodged (report), made (tax return, trustee or PD 9D application), contracts exchanged (conveyancing), the anniversary or completion (property), or the travel date (YYYY-MM-DD)."New value: +"The date for the fee: the order date (application), the anniversary (annual fees), the date lodged (report), made (tax return, trustee or PD 9D application), contracts exchanged (conveyancing), the anniversary or completion (property), or the travel date."
    • changedInput schema / properties / items / items / properties / end / description
      Previous value: -"Part year: the date it ended (YYYY-MM-DD)."New value: +"Part year: the date it ended."
    • changedInput schema / properties / items / items / properties / hours / description
      Previous value: -"Travel: the hours spent travelling, as a number such as \"12.5\" or hours and minutes such as \"3:30\"."New value: +"Travel: the hours spent travelling, in hours (e.g. \"12.5\" or \"3:30\")."
    • changedInput schema / properties / items / items / properties / kind / description
      Previous value: -"What the fee is for: \"application\" (deputy application), \"annual\" (annual fee, property and affairs), \"hw\" (annual fee, health and welfare), \"report\" (report or account to the OPG), \"tax-basic\" (basic tax return), \"tax-complex\" (complex tax return), \"trustee\" (trustee or s.18(1)(j) application), \"pd9d\" (PD 9D para 4 application), \"property\" (annual property management, public authority rates), \"conveyancing\" (conveyancing), \"travel\" (travel time)."New value: +"What the fee is for: \"application\" (deputy application), \"annual\" (annual fee, property and affairs), \"hw\" (annual fee, health and welfare), \"report\" (report or account to the OPG), \"tax-basic\" (basic tax return), \"tax-complex\" (complex tax return), \"trustee\" (trustee or s.18(1)(j) application), \"pd9d\" (PD 9D para 4 application), \"property\" (annual property management, public authority rates), \"conveyancing\", \"travel\" (travel time)."
    • changedInput schema / properties / items / items / properties / liabilities / description
      Previous value: -"Annual fees: P's total liabilities at the same date, in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Annual fees: P's total liabilities at the same date, in pounds (e.g. \"12500.50\")."
    • changedInput schema / properties / items / items / properties / start / description
      Previous value: -"Part year: the date the management year started (the order date or the last anniversary) (YYYY-MM-DD)."New value: +"Part year: the date the management year started (the order date or the last anniversary)."
    • changedInput schema / properties / wip / description
      Previous value: -"Assessment: work in progress for the management year (your figure), in pounds, e.g. \"12500\" or \"12,500.50\"."New value: +"Assessment: work in progress for the management year (your figure), in pounds (e.g. \"12500.50\")."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds substantial context beyond that: every figure is a maximum, versions differ by period, part years and VAT are handled, and the assessment branch returns SCCO fee, 75% cap, and time limit rather than an estimate.

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-loads the purpose and remains information-dense, but the long fee-by-fee list largely repeats the items.kind enum, and the final sentence about DMD Costs not acting in CoP matters does not help invocation. It is still appropriately sized for a complex legal calculator.

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 nine parameters, no output schema, and complex PD 19B rules, the description covers versions, maxima, fee categories, and the detailed-assessment branch. Remaining gaps are response-format detail and explicit coverage of lay deputies and inter-partes, which the schema partly handles.

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 the schema already documents each parameter and enum. The description adds meaningful domain detail for annual fees (net-assets percentage below £20,300) and flags part years and VAT, though it does not further clarify elect or inter-partes beyond the schema.

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 resource: works out Court of Protection deputy fixed costs under PD 19B, with versions and fee-by-fee coverage. The PD 19B and P's estate framing clearly distinguish it from civil fixed-cost calculators and other cost tools.

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 domain context for when the tool applies: CoP PD 19B, 2024 and December 2017 versions, and fixed versus detailed assessment. It does not explicitly name sibling alternatives such as calculate_fixed_costs or state when not to use it, so routing relies on the scope statement.

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