openlex-mcp

Overview Schema Source Related Servers Discussions Admin

openlex__zhlaw_find_education_laws

Read-onlyIdempotent

Find Zurich education laws (412.x) covering schools, teachers, kindergarten, special education, and day structures for focused cantonal legislation searches.

Instructions

Sucht gezielt im Zürcher Bildungsrecht (Ordnungsnummern 412.x).

<use_case>Bevorzuge dieses Tool gegenüber openlex__zhlaw_search_laws wenn die Anfrage klar im Bildungsbereich liegt (Schule, Lehrpersonen, Kindergarten, Sonderpädagogik, Tagesstrukturen). Schneller und präziser als die allgemeine Suche, da nur die 412.x-Serie (VSG, VSV, LPG, LPVO, VSM u.a.) durchsucht wird.</use_case>

<important_notes>Sucht ausschliesslich in aktiven 412.x-Gesetzen. Bei keinen Treffern: automatischer Fallback auf alle Rechtsgebiete mit Hinweis im message- Feld. Für Artikel innerhalb eines gefundenen Gesetzes: openlex__zhlaw_search_articles. Synergie: Fundstelle + swiss-courts-mcp → Rechtsprechung finden.</important_notes>

query='Elternrat', limit=10

Input Schema

Name	Required	Description	Default
`params`	Yes

Output 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.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: it searches only active 412.x laws and, crucially, falls back automatically to all legal areas with a hint in the message field when no hits occur.

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?

The XML-style tags (use_case, important_notes, example) front-load the routing decision and fallback behavior efficiently. Content is tight, though the tag scaffolding is slightly heavier than a plain sentence would need.

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 an output schema present, return values need not be explained. The description still covers fallback behavior, cross-tool routing, and a synergy note (swiss-courts-mcp) — enough for an agent to call it correctly. Only minor gaps (limit semantics) remain.

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?

The single required parameter 'query' is already well documented in the schema (subjects, examples). The description repeats the 412.x scoping and adds a usage example (query='Elternrat', limit=10), but adds little semantic detail beyond the schema, and the optional 'limit' parameter is not addressed. With the schema carrying the query semantics, baseline 3 is appropriate.

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 (Sucht) plus resource (Zürcher Bildungsrecht, Ordnungsnummern 412.x), giving scope precisely. It explicitly distinguishes itself from the general sibling search_laws by contrasting the narrow 412.x-series with the full corpus.

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> block names the alternative (openlex__zhlaw_search_laws) and the exact condition for choosing this tool (query clearly in the education domain: Schule, Lehrpersonen, Kindergarten, Sonderpädagogik, Tagesstrukturen). It also routes article-level lookups to openlex__zhlaw_search_articles, leaving nothing to inference.

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

Deploy Server