Skip to main content
Glama
Sign In

nu:legal Deutsches Recht

by eu.nulegal
OverviewDiscussionsAdmin

List cited authorities

listCitedAuthorities
Read-onlyIdempotent

What one decision cites: the provisions (with how often) and the decisions it relies on. Example: {"case": "bgh/2017-03-29/viii-zr-45-16"}

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.
offsetNoSkip this many cited decisions (pages of 50). Follow `pagination.next_offset`.

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"
-]New value: +[
+  "bgh/2017-03-29/viii-zr-45-16"
+]
  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 / case / examples
      Added value: +[
+  "KORE313182017"
+]
  4. Changed1 schema field changed
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many cited decisions (pages of 50). Follow `pagination.next_offset`.",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}
  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. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description carries a lighter burden. It adds genuine content beyond that by disclosing the shape of the return payload: provisions with citation frequency plus the relied-upon decisions. Remaining gaps like pagination are handled by the schema's offset description.

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?

Two tightly packed sentences: the purpose is front-loaded and the example immediately follows as concrete grounding. No filler, no redundant restatement of the title.

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 must convey what comes back, and it does state the two result categories (provisions with counts, cited decisions). Fully complete treatment would also mention result ordering or pagination at a behavioral level, though the offset parameter's schema description largely covers paging.

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%, so the schema already documents the case identifier formats, the language default, and the offset/paging semantics thoroughly. The description repeats the case example already present in the schema and adds no new parameter meaning, which is the baseline expectation when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb-like operation and resource: 'What one decision cites: the provisions (with how often) and the decisions it relies on.' This clearly conveys the direction of the citation traversal. It does not, however, explicitly name the sibling listCitingDecisions as the inverse operation, so the agent must infer the distinction from the wording alone.

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

Usage Guidelines3/5

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

Usage is only implied: the phrase 'What one decision cites' signals that this tool answers an outgoing-citations question, which implicitly contrasts with listCitingDecisions. There is no explicit 'use this when…' statement, no exclusion, and no mention of alternatives for reverse lookups.

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