Skip to main content
Glama
Sign In

Open Legal Data (Germany)

by io.openlegaldata
OverviewDiscussionsAdmin

Validate legal citation

validate_citation
Read-onlyIdempotent

Check if a legal citation exists in the OLDP database.

    Validates Aktenzeichen (file numbers), ECLI identifiers, or
    paragraph references (e.g. "§ 823 BGB"). Use this to verify
    citations before presenting them to users.

    Args:
        citation: The citation to validate (e.g. "VI ZR 123/22",
            "ECLI:DE:BGH:2023:...", "§ 823 BGB").
        citation_type: Type hint: "auto" (default), "file_number",
            "ecli", or "law_reference".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "citation": "<citation>"
    },
    "name": "validate_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYes
citation_typeNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive, non-open-world operation. The description adds the database scope and the accepted citation forms, but it does not describe return behavior, failure modes, or what happens with malformed citations.

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 core purpose is front-loaded and the Argument block is efficient. The indented docstring formatting and repeated validation wording add slight structural noise but no major waste.

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?

For a low-complexity, two-parameter validation tool with strong safety annotations, the description covers purpose, input examples, type options, and usage context. It leaves return values and error semantics unspecified, which is a modest gap given the absence of an output schema.

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%, so the description carries the full burden for the two parameters. It provides concrete citation examples and enumerates all allowed citation_type values including the default, though it does not explain how 'auto' detection works.

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: checking whether a legal citation exists in the OLDP database. It does not explicitly distinguish itself from sibling search/get tools, so it falls short of the top score for sibling differentiation.

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?

It gives clear usage context with 'Use this to verify citations before presenting them to users,' which tells the agent when this tool is appropriate. It does not name alternatives or when-not-to-use conditions.

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