Skip to main content
Glama

Open Legal Data (Germany)

Get court decision

get_case
Read-onlyIdempotent

Retrieve a court case by ID or slug.

    By default returns the case metadata and the complete, untruncated
    ``content`` as plain text (HTML tags removed, entities decoded,
    whitespace normalized; one line per paragraph, Randnummern as line
    prefix). To read a long decision piece by piece, request a snippet
    with ``offset`` and/or ``length``; both count characters of that
    plain text. In snippet mode ``content`` is omitted and a ``snippet``
    object is returned:
    ``text``, ``offset``, ``length``, ``total_length``, ``has_more`` and
    ``next_offset``. Pass ``next_offset`` as ``offset`` to continue
    reading until ``has_more`` is false.

    Args:
        case_id: Case database ID.
        slug: Case URL slug.
        offset: Start position in plain-text characters (default 0).
        length: Number of plain-text characters to return. 0 (default)
            means "until the end". Leave both at 0 for the full content.
        full_text: Deprecated and ignored (content is never truncated).
            Passing it adds a ``deprecation_warnings`` entry to the
            response.
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
lengthNo
offsetNo
case_idNo
full_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (read-only, idempotent, non-destructive), and the description adds substantial behavior: HTML tags stripped, entities decoded, whitespace normalized, Randnummern as line prefixes, character-based offsets, snippet mode omitting content, and the deprecation_warnings side effect. Small gap: it doesn't say what the metadata fields are or what an invalid case_id/slug yields.

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 core action, then a mode/snippet contract, then a parameter block; every section is purposeful. Minor redundancy in restating defaults ('Leave both at 0 for the full content') and in re-listing parameter names already in the schema, but the added semantics justify the length.

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?

For a read-only fetch with no output schema, the description supplies everything needed to call it correctly and to interpret the snippet response shape (text, offset, length, total_length, has_more, next_offset). Pagination, deprecation, and text-normalization semantics are all covered.

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?

Schema description coverage is 0%, so the description carries the full burden and does so: case_id, slug, offset (default 0), length (0 = to the end), and full_text marked deprecated and ignored with its side effect on the response. It even specifies that offsets count characters of the normalized plain text, which the schema cannot convey.

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 ('Retrieve a court case') plus the identifier basis ('by ID or slug'), which cleanly separates it from search_cases or get_citing_cases siblings. It also defines the default payload (metadata plus full untruncated content).

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?

Clearly explains the two operating modes: default full retrieval versus piece-by-piece reading via offset/length, including the continuation rule using next_offset until has_more is false. It does not route the agent from alternatives (e.g. how to obtain a case_id/slug in the first place), so no explicit when-not-to-use guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.