Lex — Temporal Luxembourg and EU Law

article_history

The history of one article of a Luxembourg act across its states.

Input Schema

Name	Required	Description	Default
`anchor`	Yes
`language`	No
`identifier`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 27, 2026

removedInput schema / properties / anchor / description

Removed value: -"provision anchor, e.g. art_1er (find it via search or as_of mode=outline)"

removedInput schema / properties / anchor / maxLength
```
Removed value: -512
```
addedInput schema / properties / anchor / pattern
```
Added value: +"\\S"
```

removedInput schema / properties / from_date

Removed value: -{
-  "description": "optional ISO date: keep only the states in force at or after it",
-  "maxLength": 10,
-  "minLength": 1,
-  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$",
-  "type": "string"
-}

addedInput schema / properties / identifier

Added value: +{
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}

removedInput schema / properties / language / description

Removed value: -"optional language code; defaults to the work's primary derived language"

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": "optional ISO date: keep only the states that began on or before it",
-  "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 / 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",
-  "anchor"
-]New value: +[
+  "identifier",
+  "anchor"
+]

Changed2 schema fields changedAug 17, 2026

addedInput schema / properties / from_date

Added value: +{
+  "description": "optional ISO date: keep only the states in force at or after it",
+  "maxLength": 10,
+  "minLength": 1,
+  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$",
+  "type": "string"
+}

addedInput schema / properties / to_date

Added value: +{
+  "description": "optional ISO date: keep only the states that began on or before it",
+  "maxLength": 10,
+  "minLength": 1,
+  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$",
+  "type": "string"
+}

Changed9 schema fields changedAug 11, 2026

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 / 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"
+}

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
```

Changed1 schema field changedAug 7, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "optional language code; defaults to the work's primary derived language",
+  "type": "string"
+}

First observedAug 7, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'History' implies a read-only temporal view, but it does not explain what 'states' means, whether all versions are included, how results are ordered, or whether pagination or authorization constraints apply.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of filler, but it is too terse for a three-parameter tool with no annotations and no documented schema fields. Its concision comes at the cost of necessary specification.

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?

For a tool with three parameters, zero schema descriptions, no annotations, and no output schema, the description is materially incomplete. It conveys the domain concept but omits parameter meanings, expected behavior, and return characteristics needed to invoke it confidently.

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%, and the description never names the parameters. It hints at a two-level lookup ('article' and 'act'), which may loosely map to anchor and identifier, but anchor and language remain unexplained and no format or accepted values are given.

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?

The description identifies a specific resource: the history of one article of a Luxembourg act across its states. It is clear enough to distinguish a historical article lookup from broad siblings like search or browse, but it does not explicitly distinguish it from timeline, diff, 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?

It gives no explicit guidance on when to use this tool rather than timeline, diff, changes_in_period, or as_of. The intended usage is only implied by the phrase 'history of one article.'

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 tools Inspect

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.

article_history

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources