Skip to main content
Glama

Gesetz: Übersicht, Gliederung, Änderungen

gesetz
Read-onlyIdempotent

Ein ganzes Gesetz ohne Normtexte: info (Titel, Stand, Normenzahl), Gliederung, Änderungen seit einem Datum oder Nummerierungslücken. rechtsnatur: Verwaltungsvorschrift – bindet die Verwaltung, nicht Gerichte und Bürger.

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": {
      "law": "<law>"
    },
    "name": "gesetz"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYesKürzel, Groß-/Kleinschreibung egal: 'BGB', 'BayBO'.
limitNostruktur/aenderungen: 1–500 je Seite.
offsetNoBlättern: next_offset der Vorantwort.
ansichtNo'info' (Titel, Stand, Normenzahl), 'struktur' (Gliederung, word_count je Norm), 'aenderungen' (seit since_date; geaendert_am = Tag, an dem Zitierfest die Textänderung erfasst hat, nicht Inkrafttreten), 'luecken' (fehlende oder weggefallene Nummern).info
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.
since_dateNoaenderungen: ab Datum (ISO), Standard vor einem Monat.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / ansicht / description
      Previous value: -"'info' (Titel, Stand, Normenzahl), 'struktur' (Gliederung, word_count je Norm), 'aenderungen' (seit since_date), 'luecken' (fehlende oder weggefallene Nummern)."New value: +"'info' (Titel, Stand, Normenzahl), 'struktur' (Gliederung, word_count je Norm), 'aenderungen' (seit since_date; geaendert_am = Tag, an dem Zitierfest die Textänderung erfasst hat, nicht Inkrafttreten), 'luecken' (fehlende oder weggefallene Nummern)."
  2. Changed1 schema field changed
    • 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."
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that no norm texts are returned (a meaningful result-scope trait), but it does not mention pagination behavior or the meaning of geaendert_am versus Inkrafttreten — those caveats live only in the schema text.

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?

Two compact sentences, front-loaded with the payload list before the scope exclusion. The second sentence on rechtsnatur is tangential to invoking the tool and sits oddly as a standalone claim, which costs slightly against a perfect score.

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 6-parameter, read-only, non-paginated-explicit tool with no output schema, the description conveys what each view returns (Titel/Stand/Normenzahl, word_count per Norm, missing numbers) well enough to call it correctly. Gaps are minor: no explicit statement of the return envelope or of what `rechtsraum` does at a high level, though the schema covers the latter.

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 `ansicht`, `limit`, `offset`, `rechtsraum` and `since_date` are already fully documented, including the important geaendert_am caveat. The description mirrors the view list (info/Gliederung/Änderungen/Lücken) without adding format or edge-case guidance beyond the schema, 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 states the resource (a whole law) and precisely enumerates the payloads available (info, Gliederung, Änderungen, Nummerierungslücken), and explicitly excludes Normtexte, which routes an agent away from the `normen` sibling. The only weakness is that the verb is implicit ('Ein ganzes Gesetz...' rather than 'Retrieve...'). The trailing rechtsnatur note adds domain framing but is not part of the tool's purpose statement.

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 Normtexte' implies that full norm texts belong to another tool, but no sibling is named and no explicit when-to-use / when-not-to-use rule is given. The view descriptions ('seit einem Datum') hint at selection criteria but leave the agent to infer the routing against `normen`, `stand`, `gesetze_finden` and `suche`.

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