openlex-mcp

Overview Schema Source Related Servers Discussions Admin

openlex__zhlaw_list_laws

Read-onlyIdempotent

Lists Zurich laws with optional filter by legal area to provide a structured overview of statutes, e.g., all active education laws. Returns titles, abbreviations, SR numbers, and status.

Instructions

Listet Zürcher Gesetze auf mit optionalem Filter nach Rechtsgebiet.

Wenn eine strukturierte Übersicht aller Gesetze eines Rechtsgebiets benötigt wird (z.B. alle aktiven Bildungsgesetze). Für gezielte Textsuche ist openlex__zhlaw_search_laws besser; für reines Bildungsrecht openlex__zhlaw_find_education_laws.

sr_prefix filtert nach Ordnungsnummer-Prefix (412=Bildung, 331=Steuern, 700=Bau, 131=Verfassung, 810=Gesundheit). active_only=True blendet aufgehobene Gesetze aus. Unterstützt Paginierung via offset. Gibt Titel, Abkürzung, SR-Nummer und Status zurück — keinen Volltext.

sr_prefix='412', active_only=True, limit=50

Input Schema

TableJSON Schema

Name	Required	Description	Default
`params`	Yes

Output Schema

TableJSON Schema

Name	Required	Default
`count`	No
`source`	No	Kanton Zürich Rechtssammlung — HuggingFace rcds/swiss_legislation (CC-BY-SA 4.0) & zh.ch
`message`	No
`results`	No
`provenance`	Yes
`corpus_note`	No	Bestandsstand 2023-01-01 — die jüngste Fassung im Datensatz stammt von diesem Datum. Spätere Änderungen und Aufhebungen fehlen; ein zwischenzeitlich aufgehobenes Gesetz erscheint weiterhin als in Kraft. Für den geltenden Wortlaut den ZH-Lex-Permalink konsultieren.
`result_type`	No	law_summaries
`corpus_as_of`	No	2023-01-01

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.0Sep 30, 2026

addedOutput schema / properties / corpus_as_of

Added value: +{
+  "default": "2023-01-01",
+  "title": "Corpus As Of",
+  "type": "string"
+}

addedOutput schema / properties / corpus_note

Added value: +{
+  "default": "Bestandsstand 2023-01-01 — die jüngste Fassung im Datensatz stammt von diesem Datum. Spätere Änderungen und Aufhebungen fehlen; ein zwischenzeitlich aufgehobenes Gesetz erscheint weiterhin als in Kraft. Für den geltenden Wortlaut den ZH-Lex-Permalink konsultieren.",
+  "title": "Corpus Note",
+  "type": "string"
+}

First observedv0.2.3Jul 29, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds genuine behavior beyond that: sr_prefix semantics, active_only hiding repealed laws, offset-based pagination, and a clear disclosure that the result is metadata (Titel, Abkürzung, SR-Nummer, Status) and NOT full text.

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?

Tags (use_case, important_notes, example) keep it front-loaded and skimmable, and every sentence carries routing, filter semantics, or return-shape information with no filler.

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?

For a paginated list tool with annotations covering safety, the description supplies routing, filter semantics, pagination, and the explicit 'kein Volltext' return scope. Together with the output schema, an agent has everything needed to call it correctly.

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?

Per the signal, schema description coverage is low, so the description must compensate. It does: it explains sr_prefix as an Ordnungsnummer prefix with real codes (412, 331, 700, 131, 810), confirms active_only semantics, and shows limit/offset usage in the example, adding meaning beyond the bare schema.

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 (auflisten) and resource (Zürcher Gesetze) with the scoping detail 'optionaler Filter nach Rechtsgebiet'. The use_case block explicitly differentiates from siblings search_laws and find_education_laws, so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The use_case names the exact condition to pick this tool (structured overview of all laws in a legal area) and names the two alternatives with their own selecting conditions (targeted text search, education-only). Routing is fully specified.

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

Deploy Server