Skip to main content
Glama

Zitierfest

by de.zitierfest
OverviewDiscussionsAdmin

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.

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', '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. 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'."
  2. 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'."
  3. 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."
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower. The description still adds non-obvious behavior: typo tolerance, the no-filter default of listing holdings per source, and the return shape (laws by relevance, matched, next_offset). Pagination behavior is implied via next_offset but not fully spelled out.

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 short clauses, zero filler, and the searchable facets are front-loaded before the default behavior and the response shape. Every sentence earns its place.

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 six optional parameters, no output schema, and rich per-parameter descriptions, the description covers purpose, defaults, and return fields adequately. A sentence on how the facet parameters interact or on paging limits would close the remaining gap.

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 100%, so the baseline is 3; the description earns an extra point by enumerating the four facet dimensions (Titelwort, Normgeber, Rechtsraum, Quelle) in the order they matter and flagging that the filters combine. It does not add format detail beyond the schema, which is fine given full coverage.

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?

States a specific action and resource: find laws and abbreviations by title word, normgiver, legal space, or source. The four named facets make the scope concrete. It does not name or contrast with any sibling (gesetz, normen, suche), so the agent must infer that this is the multi-facet search entry point.

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?

'Ohne Angabe: Bestand je Quelle' tells the agent what happens with no filters, which is real usage guidance for the default path. But there is no explicit when-to-use-this-vs-sibling guidance, even though 'gesetz', 'normen', and 'suche' sit right next to it.

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

All Zitierfest 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