Skip to main content
Glama
Sign In

Open Legal Data (Germany)

by io.openlegaldata
OverviewDiscussionsAdmin

Get court details

get_court
Read-onlyIdempotent

Get detailed information about a specific court.

    Look up a court by ID, slug, or code. Returns full details including
    address, contact information, and case count.

    Args:
        court_id: Court database ID.
        slug: Court slug (e.g. "ag-charlottenburg").
        code: Court ECLI code (e.g. "AGBECH" for the Amtsgericht
            Charlottenburg, "BGH").

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_court"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNo
slugNo
court_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely useful return-value context (address, contact information, case count) that annotations cannot express, but it is silent on a key behavioral question: all three parameters are optional with defaults (0 and empty strings), so the description never says what happens if none is supplied or if several are supplied at once.

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?

The lead sentence front-loads purpose, followed by lookup keys and return payload, with zero filler. The Args block is docstring-derived and slightly redundant in format, but each line contributes real parameter meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 correctly states what is returned. For a three-optional-parameter lookup tool, though, it is incomplete on resolution behavior: nothing about which key wins when multiple are passed, the sentinel defaults, or not-found handling.

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?

Schema description coverage is 0% and the schema only carries bare titles, so the description carries the full burden and does so well, documenting all three parameters with concrete examples for slug ("ag-charlottenburg") and ECLI code ("AGBECH", "BGH"). It does not specify precedence or mutual exclusivity among the three keys, or the meaning of the zero/empty-string defaults, which is the main residual gap.

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?

The description states a specific verb and resource ("Get detailed information about a specific court") and enumerates the three lookup keys, which distinguishes it from the sibling list_courts. It stops short of explicitly naming the alternative, so an agent must infer that list_courts is the browse path.

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 implied by the lookup-key framing: an agent with a known ID, slug, or ECLI code should use this tool. However, there is no explicit when-to-use statement, no pointer to list_courts for discovering an identifier, and no guidance on what to do when the identifier is unknown.

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

All Open Legal Data (Germany) 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