Skip to main content
Glama

Lex — Temporal Luxembourg and EU Law

by io.github.SFHAJJI
OverviewDiscussionsAdmin

as_of

The state of a Luxembourg act applicable on a date (publisher), with its articles; for an EU act, the wording dated at or before the date (an EU wording date, never an applicability date).

Input Schema

NameRequiredDescriptionDefault
dateYes
languageNo
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • removedInput schema / allOf
      Removed value: -[
-  {
-    "if": {
-      "properties": {
-        "mode": {
-          "const": "select"
-        }
-      },
-      "required": [
-        "mode"
-      ]
-    },
-    "then": {
-      "required": [
-        "anchors"
-      ]
-    }
-  }
-]
    • removedInput schema / properties / anchors
      Removed value: -{
-  "description": "optional comma-separated provision anchors for mode=outline; required for mode=select, e.g. art_1er,art_33",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / date / description
      Removed value: -"ISO date YYYY-MM-DD"
    • removedInput schema / properties / date / maxLength
      Removed value: -10
    • removedInput schema / properties / date / minLength
      Removed value: -1
    • changedInput schema / properties / date / pattern
      Previous value: -"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$"New value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}$"
    • addedInput schema / properties / identifier
      Added value: +{
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}
    • removedInput schema / properties / language / description
      Removed value: -"optional language code, e.g. fr"
    • removedInput schema / properties / language / maxLength
      Removed value: -16
    • addedInput schema / properties / language / pattern
      Added value: +"\\S"
    • removedInput schema / properties / mode
      Removed value: -{
-  "description": "full | outline | select (default full)",
-  "enum": [
-    "full",
-    "outline",
-    "select"
-  ],
-  "maxLength": 64,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / publisher
      Removed value: -{
-  "description": "publisher id; required when work is not publisher-qualified",
-  "maxLength": 64,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / version_key
      Removed value: -{
-  "description": "optional opaque key returned by timeline or an ambiguous_version choice",
-  "maxLength": 128,
-  "minLength": 1,
-  "type": "string"
-}
    • removedInput schema / properties / work
      Removed value: -{
-  "description": "Work-level lex_id (publisher:workkey), version-level lex_id (version segment ignored), or verbatim publisher identifier with publisher supplied. Unknown document -> call search first.",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "work",
-  "date"
-]New value: +[
+  "identifier",
+  "date"
+]
  2. Changed3 schema fields changed
    • addedInput schema / allOf
      Added value: +[
+  {
+    "if": {
+      "properties": {
+        "mode": {
+          "const": "select"
+        }
+      },
+      "required": [
+        "mode"
+      ]
+    },
+    "then": {
+      "required": [
+        "anchors"
+      ]
+    }
+  }
+]
    • changedInput schema / properties / date / pattern
      Previous value: -"^[0-9]{4}-[0-9]{2}-[0-9]{2}$"New value: +"^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$"
    • addedInput schema / properties / version_key
      Added value: +{
+  "description": "optional opaque key returned by timeline or an ambiguous_version choice",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  3. Changed15 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / anchors / maxLength
      Added value: +1000
    • addedInput schema / properties / anchors / minLength
      Added value: +1
    • addedInput schema / properties / date / maxLength
      Added value: +10
    • addedInput schema / properties / date / minLength
      Added value: +1
    • addedInput schema / properties / date / pattern
      Added value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}$"
    • addedInput schema / properties / language / maxLength
      Added value: +16
    • addedInput schema / properties / language / minLength
      Added value: +1
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "full",
+  "outline",
+  "select"
+]
    • addedInput schema / properties / mode / maxLength
      Added value: +64
    • addedInput schema / properties / mode / minLength
      Added value: +1
    • addedInput schema / properties / publisher
      Added value: +{
+  "description": "publisher id; required when work is not publisher-qualified",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / work / description
      Previous value: -"Work-level lex_id (publisher:workkey), version-level lex_id (version segment ignored), or verbatim publisher identifier. Unknown document -> call search first."New value: +"Work-level lex_id (publisher:workkey), version-level lex_id (version segment ignored), or verbatim publisher identifier with publisher supplied. Unknown document -> call search first."
    • addedInput schema / properties / work / maxLength
      Added value: +1000
    • addedInput schema / properties / work / minLength
      Added value: +1
  4. Changed1 schema field changed
    • changedInput schema / properties / anchors / description
      Previous value: -"comma-separated provision anchors for mode=select, e.g. art_1er,art_33"New value: +"optional comma-separated provision anchors for mode=outline; required for mode=select, e.g. art_1er,art_33"
  5. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description must carry the whole burden, and it does add genuine semantics: for EU acts the date resolves to a wording date at or before the requested date, explicitly never an applicability date. That is a real disambiguation of a subtle behavior. Still missing: that this is a read-only retrieval, how large the returned article set may be, and what happens when no wording exists at or before the date.

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?

A single dense sentence with no filler; the core temporal rule is front-loaded. The compression goes slightly too far, producing cryptic fragments like '(publisher)' that cost more clarity than the tokens they save.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No annotations, no output schema, and 0% schema description coverage for a domain-specific legal tool. An agent still cannot tell which identifier formats are valid, what 'language' does, or how this differs from four sibling temporal tools, which is a substantial gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across three parameters, so the description must compensate. It clarifies the semantics of 'date' only indirectly through the EU wording rule, and says nothing about the accepted form of 'identifier' (ELI, CELEX, act number?) or what 'language' controls. Two of three parameters remain opaque.

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?

Names the specific resource (the state of a Luxembourg/EU act on a date, with its articles) and distinguishes the two legal regimes the tool handles. However, it does not differentiate itself from near-identical siblings like in_force_on, status_on, and as_observed, and the parenthetical '(publisher)' is unexplained.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool rather than in_force_on, status_on, as_observed, or timeline, all of which occupy adjacent temporal territory. The Luxembourg-vs-EU split is a usage hint, but it is embedded in a purpose clause rather than framed as guidance.

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

All Lex — Temporal Luxembourg and EU Law toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources