Skip to main content
Glama
Sign In

nu:legal Deutsches Recht

by eu.nulegal
OverviewDiscussionsAdmin

List case passages

listCasePassages
Read-onlyIdempotent

Read a decision: its paragraphs, each with the court's Randnummer (rn) and a link. case takes an ECLI, our decision URL or an Aktenzeichen. Jump to a Randnummer with around, page with offset and limit. The first page also says how often the decision is cited and by whom. The answer carries card: typed headnotes (Leitsatz apart from Orientierungssatz), the tenor where the source marks it, cited_norms, fundstellen, cite_as; never generated text. Example: {"case": "bgh/2017-03-29/viii-zr-45-16", "around": 15, "limit": 5}

Input Schema

NameRequiredDescriptionDefault
caseYesA stored decision id, an ECLI, or this site's decision URL as `search` returns it. The canonical decision key `{court}/{date}/{slug}` (e.g. `bgh/2024-07-10/viii-zr-276-23`) is accepted wherever a decision is named; a key that names two decisions answers `ambiguous` with `candidates`.
langNoLanguage of the decision text: 'de' or 'en'. Default: German when it exists, else English.
limitNo
aroundNoA Randnummer as the court printed it. Returns a window of `limit` passages centred on it. Not combinable with `offset`.
offsetNo
includeNo`["proceeding"]` adds `proceeding`: the Verfahrensgang (earlier and later decisions of the same proceeding) as the courts' records state it. No outcome is stated.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / case / description
      Previous value: -"A juris doknr, an ECLI, or this site's decision URL as `search` returns it. The canonical decision key `{court}/{date}/{slug}` (e.g. `bgh/2024-07-10/viii-zr-276-23`) is accepted wherever a doknr is; a key that names two decisions answers `ambiguous` with `candidates`."New value: +"A stored decision id, an ECLI, or this site's decision URL as `search` returns it. The canonical decision key `{court}/{date}/{slug}` (e.g. `bgh/2024-07-10/viii-zr-276-23`) is accepted wherever a decision is named; a key that names two decisions answers `ambiguous` with `candidates`."
    • changedInput schema / properties / case / examples
      Previous value: -[
-  "KORE313182017",
-  "ECLI:DE:BGH:2017:290317UVIIIZR45.16.0"
-]New value: +[
+  "bgh/2017-03-29/viii-zr-45-16",
+  "ECLI:DE:BGH:2017:290317UVIIIZR45.16.0"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / case / description
      Previous value: -"A juris doknr, an ECLI, or this site's decision URL as `search` returns it."New value: +"A juris doknr, an ECLI, or this site's decision URL as `search` returns it. The canonical decision key `{court}/{date}/{slug}` (e.g. `bgh/2024-07-10/viii-zr-276-23`) is accepted wherever a doknr is; a key that names two decisions answers `ambiguous` with `candidates`."
  3. Changed1 schema field changed
    • addedInput schema / properties / include
      Added value: +{
+  "description": "`[\"proceeding\"]` adds `proceeding`: the Verfahrensgang (earlier and later decisions of the same proceeding) as the courts' records state it. No outcome is stated.",
+  "items": {
+    "enum": [
+      "proceeding"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / case / examples
      Added value: +[
+  "KORE313182017",
+  "ECLI:DE:BGH:2017:290317UVIIIZR45.16.0"
+]
  5. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Language of the decision text: 'de' or 'en'. Default: German when it exists, else English.",
+  "enum": [
+    "de",
+    "en"
+  ],
+  "type": "string"
+}
  6. Changed2 schema fields changed
    • addedInput schema / properties / around
      Added value: +{
+  "description": "A Randnummer as the court printed it. Returns a window of `limit` passages centred on it. Not combinable with `offset`.",
+  "examples": [
+    51,
+    "12"
+  ],
+  "type": [
+    "integer",
+    "string"
+  ]
+}
    • changedInput schema / properties / limit / default
      Previous value: -100New value: +30
  7. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: passages are verbatim and 'never generated text', the first page carries citation counts with citers, and Leitsatz is kept apart from Orientierungssatz. It does not cover error or edge behavior beyond what the schema already says about ambiguous keys.

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?

Purpose is front-loaded in the first clause, and the dense backtick-heavy sentences each convey a distinct fact (input forms, navigation, first-page citations, card contents). Slightly compressed phrasing around `card` costs a little readability but nothing is padding.

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?

With no output schema, the description does real work by naming the response fields (`rn`, link, citation info, typed `card` members) and giving a worked example call. It stops short of describing pagination totals or the overall response envelope, which an agent would still have to discover at runtime.

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?

At 67% schema coverage the schema carries most of the load, but the description adds workflow semantics — `around` as a jump-to-Randnummer window, `limit` as page size — plus a concrete combined example that shows how the parameters compose. `lang` and `include` are left entirely to the schema, so it is not fully compensating.

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 — 'Read a decision: its paragraphs, each with the court's Randnummer and a link' — which is unmistakably distinct from siblings like search or listCitingDecisions. The opening clause alone tells an agent what it gets back.

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?

Explains the navigation modes (jump with `around`, page with `offset`/`limit`) and notes that `case` accepts an ECLI, URL, or Aktenzeichen as `search` returns it, which implies the typical search-then-read flow. It never explicitly names an alternative tool or states when not to use this one, so it falls short of a 5.

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

All nu:legal Deutsches Recht 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