Skip to main content
Glama

de_oldp_get_case

Read-onlyIdempotent

Retrieve the full text of a German court decision by its numeric ID or slug from Open Legal Data.

Instructions

Fetch the full text of one decision from Open Legal Data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_refYesa numeric OLDP case id (e.g. ``"521203"``) or a slug (e.g. ``"lg-nurnberg-furth-2026-05-21-8-o-486025"``) from a ``de_oldp_case_search`` result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
dateNo
ecliNo
noteNoSource: Open Legal Data (de.openlegaldata.io), a community open-data aggregator of German case law across all court levels (federal AND state courts) - database under ODbL v1.0, decisions themselves gemeinfrei per § 5 UrhG. It is NOT an official government service and does not claim completeness; for the six federal supreme/constitutional courts prefer de_rii_case_search (official, complete). OLDP's unique value is the state-court layer (Oberlandesgerichte, Landgerichte, Amtsgerichte, state administrative/social/labor/finance courts).
slugNo
contentNoFull decision text (HTML).
eli_uriYes
byte_sizeNo
court_nameNo
source_urlYes
file_numberNo
decision_typeNo
human_readable_citationNo
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds no extra behavioral details beyond these, but is consistent. A 3 is appropriate as the description does not contradict annotations and adds minimal context.

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?

A single sentence conveys the tool's purpose without any filler or redundant information.

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?

Given the simple parameter set, rich annotations, and existence of an output schema, the description is fully adequate. No further details are needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema by noting that the case_ref comes from a 'de_oldp_case_search' result. This contextualizes the parameter and aids correct usage.

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 clearly states the verb ('Fetch'), resource ('full text of one decision'), and source ('Open Legal Data'). This distinguishes it from sibling tools like 'de_oldp_case_search' (search vs. get).

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?

The description implies usage after a search (by referencing 'case_ref from a search result'), but it does not explicitly state when to use this tool versus alternatives or provide any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matematicsolutions/de-eli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server