Skip to main content
Glama
malkreide

openlex-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

openlex__zhlaw_get_law_metadata

Read-onlyIdempotent

Retrieve live metadata for a Canton Zurich law by ordering number to verify recent amendments, current PDF edition, change date, and direct ZH-Lex URL.

Instructions

Ruft aktuelle Metadaten eines Gesetzes live von zh.ch ab.

Wenn der aktuelle Stand eines Gesetzes auf zh.ch geprüft werden soll — z.B. ob es kürzlich geändert wurde, welche PDF-Version aktuell gilt oder welche ZH-Lex URL direkt verlinkt werden kann. Einziges Tool mit Live-HTTP-Aufruf; alle anderen Tools lesen den lokalen Cache.

Macht einen echten HTTP-Request an www.zh.ch (ca. 1–3 s). Erfordert Netzwerkzugang. Liefert: Seitentitel, PDF-Links, Änderungsdatum, ZH-Lex URL. Bei 404 oder Timeout: found=False mit Fehlerdetail im error-Feld. Nur Ordnungsnummern akzeptiert (kein Abkürzungs-Lookup).

sr_number='412.100'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON 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_typeNometadata
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.9/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the description's added value is the operational detail: a real HTTP request to www.zh.ch taking 1-3s, the network-access requirement, the fields returned (title, PDF links, change date, ZH-Lex URL), and explicit 404/timeout behaviour (found=False with error detail). That is rich context beyond the structured hints.

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?

Tagged sections (<use_case>, <important_notes>, <example>) front-load the moment of use, then the caveats, then a concrete example. Every sentence carries information; nothing is padding despite the length.

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, yet the description still names the returned fields and the failure shape, which is more than required. For a single-parameter, open-world network tool, an agent has everything needed to call it correctly and interpret the result.

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 description coverage is reported as 0%, so the description must carry the burden, and it largely does: it supplies an example (sr_number='412.100') and, more importantly, a constraint the schema does not encode — only Ordnungsnummern are accepted, no abbreviation lookup. It could still be clearer about format edge cases, but it meaningfully extends the bare pattern field.

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 and resource ('Ruft aktuelle Metadaten eines Gesetzes live von zh.ch ab') and immediately distinguishes itself from every sibling by declaring it is the 'Einziges Tool mit Live-HTTP-Aufruf; alle anderen Tools lesen den lokalen Cache'. An agent can classify it without opening the 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> block gives concrete triggers (checking whether a law changed, which PDF version is current, which ZH-Lex URL to link) and explicitly contrasts this tool against the cache-reading alternatives. When-to-use and when-to-use-something-else are both present.

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