Skip to main content
Glama
Germany Legal Research MCP Server

Germany Legal Research MCP Server

by jurisatlas

Search Legislation

search_legislation

Search German national statutes, acts, codes, and regulations via official legal registries; filter by enactment year and limit results for targeted legal research.

Instructions

Search Germany (DE) national legislation (statutes, acts, codes, regulations) via Gesetze im Internet (gesetze-im-internet.de) & Rechtsinformationen des Bundes and European/International legal registries.

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": {
      "query": "<query>"
    },
    "name": "search_legislation"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional enactment year filter.
limitNoMaximum number of results to return.
queryYesKeywords or statute title/number to search in Germany legislation.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the underlying sources (gesetze-im-internet.de, Rechtsinformationen des Bundes, European/International registries), which signals coverage and reliability characteristics, but it does not state read-only nature, result ranking, pagination behavior, or any rate/latency constraints.

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?

A single front-loaded sentence that identifies the verb, geography, document classes, and sources with no filler. It is dense with named registries that partly duplicate the schema's query description, but nothing is truly wasted.

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 three-parameter search tool with an output schema present and no annotations, the description covers what is searchable and where results come from, which is the essential context. The main gap is the mild tension between "Germany (DE) national legislation" and the mention of European/International registries without clarifying when each source applies.

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

Parameters3/5

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

Schema description coverage is 100%, so query, year, and limit are all documented in the schema itself (keywords or statute title/number, optional enactment year filter, max results). The description adds nothing beyond that baseline, which is acceptable given the schema does the work.

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 pairs a clear verb ("Search") with a well-scoped resource ("Germany (DE) national legislation"), and enumerates the document types (statutes, acts, codes, regulations) plus the sources queried. It implicitly separates itself from search_case_law by focusing on legislation rather than court decisions, though it never names the sibling explicitly.

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 only implied: an agent can infer this is the tool for statutes and regulations rather than case law, and that it covers DE plus European/international registries. There is no explicit when-to-use/when-not-to-use statement and no pointer to search_case_law or verify_citation as alternatives for adjacent needs.

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