Skip to main content
Glama
UK Business Tools - Ledgerhall

UK Business Tools - Ledgerhall

Get Judgment Header

law_judgment_get_header
Read-onlyIdempotent

Fetch UK court judgment metadata—parties, judges, neutral citation, court and dates—from a judgment slug. Call after case_law_search to retrieve authoritative details for that case.

Instructions

USE THIS TOOL WHEN you have a judgment slug and need metadata (parties, judges, neutral citation, court, dates).

Call case_law_search FIRST to get the slug. AFTER calling, use judgment_get_index to discover paragraphs, then judgment_get_paragraph to read specific ones. Authoritative source for UK judgment metadata.

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": {
      "slug": "<slug>"
    },
    "name": "law_judgment_get_header"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesJudgment slug from case_law_search, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450' — path segments of letters, digits, '-' or '_', no host or 'https://'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • changedInput schema / properties / slug / description
      Previous value: -"Judgment slug, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450'"New value: +"Judgment slug from case_law_search, e.g. 'uksc/2024/12' or 'ewca/civ/2023/450' — path segments of letters, digits, '-' or '_', no host or 'https://'."
    • addedInput schema / properties / slug / pattern
      Added value: +"^/?[A-Za-z0-9_\\-]+(/[A-Za-z0-9_\\-]+)+/?$"
  2. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered and the description's job is narrower. It adds the useful claim that this is the authoritative source for UK judgment metadata and positions the call inside a discovery sequence, but it says nothing about what happens with an invalid or non-existent slug.

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 trigger condition, followed by prerequisite and successor tools in execution order. It is short and mostly earns its space, though the trailing 'Authoritative source...' sentence is closer to a positioning claim than an operational instruction.

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 one-parameter read tool with rich annotations and an output schema, the description covers purpose, input provenance, and workflow placement, so no essential detail is missing. Only failure modes (bad slug, judgment not found) are left implicit.

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?

The single parameter already has 100% schema coverage including a regex pattern and two worked examples, so the baseline is 3. The description goes beyond that by stating the slug originates from case_law_search, giving the agent a provenance rule for constructing valid values rather than just a format rule.

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 names a specific verb and resource and enumerates the returned metadata (parties, judges, neutral citation, court, dates), which unambiguously separates it from law_judgment_get_index and law_judgment_get_paragraph. An agent can identify this as the header/metadata fetch in a two-step read workflow without opening the 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?

It gives an explicit trigger ('WHEN you have a judgment slug and need metadata'), a prerequisite ('Call case_law_search FIRST to get the slug'), and an explicit follow-on chain (get_index, then get_paragraph). Both when-to-use and what-to-do-next are stated rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools