Skip to main content
Glama

Lex — Temporal Luxembourg and EU Law

by io.github.SFHAJJI
OverviewDiscussionsAdmin

diff

The article-level difference between the states of a Luxembourg act on two dates.

Input Schema

NameRequiredDescriptionDefault
date_toYes
languageNo
date_fromYes
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedInput schema / properties / anchor
      Removed value: -{
-  "description": "optional held provision anchor returned by search, e.g. art_92",
-  "maxLength": 512,
-  "minLength": 1,
-  "type": "string"
-}
    • addedInput schema / properties / date_from
      Added value: +{
+  "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
+  "type": "string"
+}
    • addedInput schema / properties / date_to
      Added value: +{
+  "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
+  "type": "string"
+}
    • removedInput schema / properties / from_date
      Removed value: -{
-  "description": "ISO date",
-  "maxLength": 10,
-  "minLength": 1,
-  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$",
-  "type": "string"
-}
    • removedInput schema / properties / from_version_key
      Removed value: -{
-  "description": "optional opaque key returned by timeline or an ambiguous_version choice",
-  "maxLength": 128,
-  "minLength": 1,
-  "type": "string"
-}
    • addedInput schema / properties / identifier
      Added value: +{
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}
    • removedInput schema / properties / language / description
      Removed value: -"language code"
    • removedInput schema / properties / language / maxLength
      Removed value: -16
    • addedInput schema / properties / language / pattern
      Added value: +"\\S"
    • 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 / to_date
      Removed value: -{
-  "description": "ISO date",
-  "maxLength": 10,
-  "minLength": 1,
-  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$",
-  "type": "string"
-}
    • removedInput schema / properties / to_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",
-  "from_date",
-  "to_date"
-]New value: +[
+  "identifier",
+  "date_from",
+  "date_to"
+]
  2. Changed4 schema fields changed
    • changedInput schema / properties / from_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 / from_version_key
      Added value: +{
+  "description": "optional opaque key returned by timeline or an ambiguous_version choice",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
    • changedInput schema / properties / to_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 / to_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 / anchor / maxLength
      Added value: +512
    • addedInput schema / properties / anchor / minLength
      Added value: +1
    • addedInput schema / properties / from_date / maxLength
      Added value: +10
    • addedInput schema / properties / from_date / minLength
      Added value: +1
    • addedInput schema / properties / from_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 / publisher
      Added value: +{
+  "description": "publisher id; required when work is not publisher-qualified",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / to_date / maxLength
      Added value: +10
    • addedInput schema / properties / to_date / minLength
      Added value: +1
    • addedInput schema / properties / to_date / pattern
      Added value: +"^[0-9]{4}-[0-9]{2}-[0-9]{2}$"
    • 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
    • addedInput schema / properties / anchor
      Added value: +{
+  "description": "optional held provision anchor returned by search, e.g. art_92",
+  "type": "string"
+}
  5. First observed

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it discloses almost nothing beyond the headline operation. It does not say whether the result is a structured diff, how unchanged/repealed articles are represented, what errors occur for unknown identifiers or unsupported dates, or whether the act version must exist on both dates.

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 front-loaded sentence with no filler, and the key qualifier ('article-level') appears early. Its brevity is efficient, though it borders on under-specification given the undocumented parameters.

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?

With no annotations, no output schema, and four undocumented parameters, the description is not complete enough for correctly invoking the tool. It leaves open the identifier format, the role of 'language', and the shape of the returned difference.

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 description coverage is 0% — the properties only carry regex patterns, with no semantic text at all. The description clarifies that date_from/date_to are the two comparison dates and implies identifier refers to a Luxembourg act, but it never mentions the 'language' parameter and never specifies the expected identifier form (e.g., ELI or work URI).

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?

States a specific resource (article-level difference between states of a Luxembourg act) and a specific operation (diff over two dates), which is clearly distinct from a general listing tool. It stops short of naming how it differs from near-siblings such as article_history or changes_in_period.

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 explicit when-to-use or when-not-to-use guidance. The phrase 'on two dates' implies a comparison scenario, but with 23 siblings including article_history, changes_in_period, as_of and as_observed, an agent gets no help deciding which to pick.

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