Skip to main content
Glama
Sign In

DMD Costs legal costs tools

by io.github.Ments123
OverviewDiscussionsAdmin

DMD Costs guides and case notes

search_costs_guides
Read-onlyIdempotent

Searches the guides and case notes DMD Costs has published on legal costs in England and Wales: detailed assessment, Part 36 offers, fixed costs, payments on account, housing disrepair, clinical negligence and MoD noise-induced hearing loss (NIHL) costs, and recent costs judgments. Returns the closest articles, best first, each with its summary, key points, the dates it was published and last reviewed, and its link. Use it for background reading or the case law on a costs point, and cite the article's link; for a short answer to a costs question, a glossary term or a court form, use search_legal_costs_help.

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": "search_costs_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many articles to return, best match first: a whole number from 1 to 10 (default 5).
queryYesWhat to look for, in plain words: a costs topic, rule or case, e.g. 'payment on account percentage', 'Part 36 offer with non-money terms', 'housing disrepair costs-only proceedings' or 'Cubic v TfL'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare this is a read-only, idempotent, non-destructive search. The description adds useful behavioral detail by explaining that results are returned closest/best first and include summaries, key points, publication/review dates, and links. It does not discuss rate limits or no-result behavior, but it goes well beyond the safety profile already supplied by annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and corpus, then explains return behavior, then closes with routing guidance. Although the first sentence is long, its topic list earns its place by defining search scope precisely, and no sentence is superfluous.

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?

With no output schema, the description carries the burden of explaining return values, and it does: closest articles first, with summaries, key points, publication/review dates, and links. Combined with clear usage routing and full parameter documentation in the schema, the definition is complete enough for an agent to call it correctly.

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 both the query and limit parameters are clearly documented in the schema with examples and bounds. The prose description does not add further parameter-specific meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: it searches DMD Costs-published guides and case notes on legal costs in England and Wales. It also lists the covered subject areas and distinguishes itself from search_legal_costs_help, so an agent can tell exactly what corpus this tool searches.

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?

It explicitly says when to use it: background reading or case law on a costs point, and to cite the article link. It also names the alternative and the conditions that select it: short answers, glossary terms, and court forms should use search_legal_costs_help.

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