Skip to main content
Glama
Sign In

DMD Costs legal costs tools

by io.github.Ments123
OverviewDiscussionsAdmin

Court fee finder by form (EX50: N244, N245, N293A, N379 and more)

find_court_fee_by_form
Read-onlyIdempotent

Finds the civil court fee in England and Wales for a court form or a step, by form number or in words (for example "N244", "N245", "warrant of control", "set aside a CCJ", "Tomlin order", "charging order"): each fee with its fee number in Schedule 1 to the Civil Proceedings Fees Order 2008, when it is paid, notes with their source, and our reading, labelled as such, where neither the Order nor the EX50 ties the fee to the form. Forms with no court fee say so. Fees in force from 13 July 2026. Help with fees is not taken into account. For the fees across a whole claim, use calculate_civil_court_fees. In the structured data, amounts are in pence; the text gives pounds.

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": {
      "query": "<query>"
    },
    "name": "find_court_fee_by_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA form number or a step, e.g. "N244", "N245", "warrant of control", "set aside a CCJ" or "Tomlin order". A form number keeps only the entries for that form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover the safe-read profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description goes well beyond them: version currency ('Fees in force from 13 July 2026'), an explicit scope caveat ('Help with fees is not taken into account'), a data-format trap ('amounts are in pence; the text gives pounds'), and provenance labelling distinguishing Order/EX50-sourced notes from 'our reading'. These are exactly the behavioral facts an agent needs beyond structured fields.

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 action and resource, and every clause carries information (sources, currency, units, sibling routing). It is densely packed into a single long sentence with a heavy example parenthetical, which costs some readability, but there is little genuine filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter lookup with no output schema, the description covers what is returned (fee, Schedule 1 fee number, when it is paid, sourced notes, labelled interpretation), the version of the fee table in force, the units of the returned amounts, and the explicit non-coverage of help with fees. Nothing an agent needs to call or interpret results is missing.

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% and the single `query` parameter is fully documented, so the baseline is 3. The description still adds meaning: it clarifies that free-text step descriptions are matched as well as form numbers, and that a form number narrows results to that form's entries. Modest but real value above 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 (finds) and resource (civil court fee in England and Wales) plus the two lookup modes (form number or words), and explicitly names the sibling it is not: 'For the fees across a whole claim, use calculate_civil_court_fees.' An agent can route between find_court_fee_by_form and calculate_civil_court_fees without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative tool and the condition that selects it (whole-claim totals), and supplies concrete example queries ('N244', 'warrant of control', 'set aside a CCJ') that show the acceptable input shapes. Exclusions are also implied clearly: help with fees is out of scope, and this is a per-form lookup rather than a calculator.

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 toolsInspect
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.

Resources