Skip to main content
Glama

Gesetze finden

gesetze_finden
Read-onlyIdempotent

Gesetze und Kürzel nach Titelwort, Normgeber, Rechtsraum oder Quelle, tippfehlertolerant. Ohne Angabe: Bestand je Quelle. Antwort: laws nach Relevanz, matched, next_offset.

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

Input Schema

NameRequiredDescriptionDefault
limitNo1–500.
filterNoKürzel oder Titelwort, tippfehlertolerant: 'Bauordnung'.
offsetNoBlättern: next_offset der Vorantwort.
quelleNoAlle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'beratzhausen-ortsrecht', 'bmf-vwv', 'brak-ccbe', 'eu-leitlinien', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'tum-satzungen', 'voelkerrecht', 'vwv-bund'.
rechtsraumNoRechtsraum-Code (bund (Bund), eu, int, tarif, by (Bayern, mit Kommunalrecht), bb, be, bw, hb, he, hh, mv, ni, nw, rp, sh, sl, sn, st, th); leer = alle.
gebietskoerperschaftNoNormgeber: 'Bund', 'Bayern', 'Brandenburg', 'Berlin', 'Baden-Württemberg', 'Bremen', 'Hessen', 'Hamburg', 'Mecklenburg-Vorpommern', 'Niedersachsen', 'Nordrhein-Westfalen', 'Rheinland-Pfalz', 'Schleswig-Holstein', 'Saarland', 'Sachsen', 'Sachsen-Anhalt', 'Thüringen', 'EU', 'München', 'Regensburg', 'Beratzhausen', 'Tarifrecht', 'Bezirk'; mit filter kombinierbar.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / quelle / description
      Previous value: -"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'beratzhausen-ortsrecht', 'bmf-vwv', 'brak-ccbe', 'eu-leitlinien', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'voelkerrecht', 'vwv-bund'."New value: +"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'beratzhausen-ortsrecht', 'bmf-vwv', 'brak-ccbe', 'eu-leitlinien', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'tum-satzungen', 'voelkerrecht', 'vwv-bund'."
  2. Changed2 schema fields changed
    • changedInput schema / properties / gebietskoerperschaft / description
      Previous value: -"Normgeber: 'Bund', 'Bayern', 'Brandenburg', 'Berlin', 'Baden-Württemberg', 'Bremen', 'Hessen', 'Hamburg', 'Mecklenburg-Vorpommern', 'Niedersachsen', 'Nordrhein-Westfalen', 'Rheinland-Pfalz', 'Schleswig-Holstein', 'Saarland', 'Sachsen', 'Sachsen-Anhalt', 'Thüringen', 'EU', 'München', 'Regensburg', 'Tarifrecht', 'Bezirk'; mit filter kombinierbar."New value: +"Normgeber: 'Bund', 'Bayern', 'Brandenburg', 'Berlin', 'Baden-Württemberg', 'Bremen', 'Hessen', 'Hamburg', 'Mecklenburg-Vorpommern', 'Niedersachsen', 'Nordrhein-Westfalen', 'Rheinland-Pfalz', 'Schleswig-Holstein', 'Saarland', 'Sachsen', 'Sachsen-Anhalt', 'Thüringen', 'EU', 'München', 'Regensburg', 'Beratzhausen', 'Tarifrecht', 'Bezirk'; mit filter kombinierbar."
    • changedInput schema / properties / quelle / description
      Previous value: -"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'bmf-vwv', 'eu-leitlinien', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'voelkerrecht', 'vwv-bund'."New value: +"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'beratzhausen-ortsrecht', 'bmf-vwv', 'brak-ccbe', 'eu-leitlinien', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'voelkerrecht', 'vwv-bund'."
  3. Changed1 schema field changed
    • changedInput schema / properties / quelle / description
      Previous value: -"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'bmf-vwv', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'voelkerrecht', 'vwv-bund'."New value: +"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'bmf-vwv', 'eu-leitlinien', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'voelkerrecht', 'vwv-bund'."
  4. Changed3 schema fields changed
    • changedInput schema / properties / gebietskoerperschaft / description
      Previous value: -"Normgeber: 'Bund', 'Bayern', 'Brandenburg', 'Berlin', 'Baden-Württemberg', 'Bremen', 'Hessen', 'Hamburg', 'Mecklenburg-Vorpommern', 'Niedersachsen', 'Nordrhein-Westfalen', 'Rheinland-Pfalz', 'Schleswig-Holstein', 'Saarland', 'Sachsen', 'Sachsen-Anhalt', 'Thüringen', 'EU', 'München', 'Regensburg', 'Bezirk'; mit filter kombinierbar."New value: +"Normgeber: 'Bund', 'Bayern', 'Brandenburg', 'Berlin', 'Baden-Württemberg', 'Bremen', 'Hessen', 'Hamburg', 'Mecklenburg-Vorpommern', 'Niedersachsen', 'Nordrhein-Westfalen', 'Rheinland-Pfalz', 'Schleswig-Holstein', 'Saarland', 'Sachsen', 'Sachsen-Anhalt', 'Thüringen', 'EU', 'München', 'Regensburg', 'Tarifrecht', 'Bezirk'; mit filter kombinierbar."
    • changedInput schema / properties / quelle / description
      Previous value: -"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'bmf-vwv', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'voelkerrecht', 'vwv-bund'."New value: +"Alle Gesetze einer Quelle: 'gesetze-im-internet', 'gesetze-bayern', 'eur-lex', 'brak', 'muenchen-stadtrecht', 'muenchen-stadtrecht-neu', 'regensburg-stadtrecht', 'bmf-vwv', 'go-bund', 'landesrecht-bb', 'landesrecht-be', 'landesrecht-bw', 'landesrecht-hb', 'landesrecht-he', 'landesrecht-hh', 'landesrecht-mv', 'landesrecht-ni', 'landesrecht-nw', 'landesrecht-rp', 'landesrecht-sh', 'landesrecht-sl', 'landesrecht-sn', 'landesrecht-st', 'landesrecht-th', 'tarif-oed', 'voelkerrecht', 'vwv-bund'."
    • changedInput schema / properties / rechtsraum / description
      Previous value: -"Rechtsraum-Code (bund (Bund), eu, int, by (Bayern, mit Kommunalrecht), bb, be, bw, hb, he, hh, mv, ni, nw, rp, sh, sl, sn, st, th); leer = alle."New value: +"Rechtsraum-Code (bund (Bund), eu, int, tarif, by (Bayern, mit Kommunalrecht), bb, be, bw, hb, he, hh, mv, ni, nw, rp, sh, sl, sn, st, th); leer = alle."
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and closed-world behavior, so the bar is lower. The description still adds real context: typo-tolerant matching and the return keys (laws by relevance, matched, next_offset), which tell the agent how to paginate and interpret hits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact clauses front-load the search axes, then the default behavior, then the response shape. No filler; every phrase carries information.

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?

With no output schema, the description compensates by naming the return fields and pagination mechanism. It is complete for a 6-parameter search tool; only the relationship to the overlapping sibling search tools is left unstated.

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 the schema already documents limit, filter, offset, quelle, rechtsraum, and gebietskoerperschaft in detail. The description reinforces typo tolerance and the no-parameter default but adds no per-parameter meaning beyond that, so baseline 3 applies.

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 names a specific verb+resource (find laws) and enumerates the lookup axes: Titelwort, Normgeber, Rechtsraum, Quelle. It does not distinguish itself from siblings like gesetz, normen, or suche, so an agent cannot tell from the text alone which of those to prefer.

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?

It gives one useful usage cue — 'Ohne Angabe: Bestand je Quelle' — explaining what happens with no filters. There is no explicit when-to-use/when-not guidance relative to gesetz, normen, or suche, which overlap heavily with this tool's surface.

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.

Resources