Skip to main content
Glama
malkreide

openlex-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

openlex__zhlaw_get_law

Read-onlyIdempotent

Retrieve a Zurich law's metadata or full text by its order number or abbreviation. Use when the identifier is already known.

Instructions

Ruft ein Zürcher Gesetz anhand der Ordnungsnummer oder Abkürzung ab.

<use_case>Wenn die Ordnungsnummer oder Abkürzung eines Gesetzes bereits bekannt ist und Metadaten oder Volltext abgerufen werden sollen. Um ein Gesetz erst zu finden, openlex__zhlaw_search_laws oder openlex__zhlaw_find_education_laws vorschalten.</use_case>

<important_notes>Unterstützt LS-Nummern ('412.100') und Abkürzungen ('VSG'). include_content=True liefert den Volltext (bis 5000 Zeichen, dann truncated=True). Bei Truncation: openlex__zhlaw_get_article für einzelne Artikel verwenden. Wichtige Gesetze: VSG, LPG, PBG, StG, KV.</important_notes>

identifier='VSG', include_content=False

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
countNo
sourceNoKanton Zürich Rechtssammlung — HuggingFace rcds/swiss_legislation (CC-BY-SA 4.0) & zh.ch
messageNo
resultsNo
provenanceYes
corpus_noteNoBestandsstand 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_typeNolaw_detail
corpus_as_ofNo2023-01-01

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.0
    • 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"
+}
  2. First observedv0.2.3

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world semantics, so the safety profile is covered. The description adds real behavioral detail beyond that: include_content=True returns full text capped at 5000 characters with truncated=True, and the recommended recovery path via get_article. It still doesn't state error behavior for unknown identifiers, which keeps it short of a 5.

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?

Three clearly tagged sections with the primary purpose front-loaded in the first sentence. The list of important laws (VSG, LPG, PBG, StG, KV) is mildly gratuitous for an agent that passes an identifier, but overall there is little waste.

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?

An output schema exists, so return values need no explanation here. The description covers identifiers, the content-vs-metadata toggle, the truncation limit, and the fallback tool — everything needed to call this one-required-parameter tool 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?

Measured schema coverage is 0%, so the description must carry the parameters and largely does: it names LS numbers ('412.100') and abbreviations ('VSG') for identifier and explains what include_content=True produces. It adds meaning beyond the raw schema, though it does not enumerate every supported abbreviation the schema lists.

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 (abrufen) and resource (Zürcher Gesetz) plus the two accepted identifier forms (Ordnungsnummer or Abkürzung). It also names the sibling tools to route through when the identifier is unknown, so an agent can distinguish it from search_laws and get_law_metadata.

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 states the precondition explicitly (identifier already known) and names the alternatives (openlex__zhlaw_search_laws, openlex__zhlaw_find_education_laws) for the discovery path. The <important_notes> add a fallback route to get_article when content is truncated.

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

Deploy Server

Other Tools