Skip to main content
Glama
Sign In

Open Legal Data (Germany)

by io.openlegaldata
OverviewDiscussionsAdmin

List law books

list_law_books
Read-onlyIdempotent

List available German law books (e.g. BGB, StGB, GG).

    Returns law books with their codes, titles, and section counts.
    Use this to discover what legislation is available before searching
    for specific law sections.

    Args:
        latest_only: Only show latest revisions (default True).
        search: Search book codes and titles. Best matches come first
            (exact code, code prefix, code part, whole word in the
            title, part of a title word); ``match`` on each result says
            which. If ``search`` is exactly a book code, titles that only
            contain it inside a longer word (e.g. "BGBl." for "BGB")
            are left out.
        limit: Maximum results (default 50, max 200). Values above 200
            are clamped; the response then includes
            ``limit_clamped: true`` and the original ``requested_limit``.

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": "list_law_books"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
latest_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description adds real value beyond that: it lists returned fields and documents the limit-clamping behavior with the 'limit_clamped' and 'requested_limit' response flags. It does not describe pagination or ordering beyond search relevance.

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 purpose and return shape before the per-parameter notes, so an agent gets the essentials first. The Args block is dense but every item adds actionable detail; the parenthetical about 'BGBl.' is helpful but slightly verbose.

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?

With no output schema, the description still explains the return fields and the clamping response keys, and all three undocumented parameters are covered. An agent has everything needed to call this correctly on the first try.

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 coverage is 0%, so the description carries the full burden and does so well: it documents latest_only's default, limit's default of 50 and max of 200 with clamping semantics, and search's matching tiers plus the 'match' field on results. The only gap is that the tie-in between latest_only and revision filtering is not fully spelled out.

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 — 'List available German law books' — with concrete examples (BGB, StGB, GG) and the returned fields (codes, titles, section counts). This clearly distinguishes it from section-level siblings such as get_law_section or search_laws.

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?

Explicitly tells the agent to use it 'to discover what legislation is available before searching for specific law sections', which establishes a clear discovery-then-search workflow. It does not name the specific follow-up tool or state exclusions, so it stops short of full when/when-not guidance.

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