Lex — Temporal Luxembourg and EU Law

in_force_on

The Luxembourg works with a state applicable on a date.

Input Schema

Name	Required	Description	Default
`date`	Yes
`limit`	No
`language`	No
`identifier`	No
`after_work_key`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 27, 2026

removedInput schema / properties / act_form

Removed value: -{
-  "description": "optional legal act form",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / properties / after_work_key

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

removedInput schema / properties / binding_status

Removed value: -{
-  "description": "optional binding status",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / date / description
```
Removed value: -"ISO date"
```
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}$"

removedInput schema / properties / document_type

Removed value: -{
-  "description": "backward-compatible source document class filter",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / domain

Removed value: -{
-  "description": "legacy domain filter; current v4 indexes leave it empty",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / hierarchy

Removed value: -{
-  "description": "optional normalized legal hierarchy",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / properties / identifier

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

removedInput schema / properties / jurisdiction

Removed value: -{
-  "description": "optional jurisdiction code from index metadata, e.g. LU or EU",
-  "maxLength": 64,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / language / description
```
Removed value: -"optional language code"
```
removedInput schema / properties / language / maxLength
```
Removed value: -16
```
addedInput schema / properties / language / pattern
```
Added value: +"\\S"
```
removedInput schema / properties / limit / description
```
Removed value: -"default 50"
```
changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +200
```

removedInput schema / properties / offset

Removed value: -{
-  "description": "pagination offset",
-  "maximum": 100000,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / publisher

Removed value: -{
-  "description": "optional publisher id, e.g. lu-legilux",
-  "maxLength": 64,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / source_class

Removed value: -{
-  "description": "optional source document class",
-  "maxLength": 1000,
-  "minLength": 1,
-  "type": "string"
-}

Changed2 schema fields changedAug 17, 2026

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])$"

changedInput schema / properties / domain / description

Previous value: -"optional reviewed legal domain"New value: +"legacy domain filter; current v4 indexes leave it empty"

Changed26 schema fields changedAug 11, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / act_form / maxLength
```
Added value: +1000
```
- addedInput schema / properties / act_form / minLength
```
Added value: +1
```
- addedInput schema / properties / binding_status / maxLength
```
Added value: +1000
```
- addedInput schema / properties / binding_status / 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 / document_type / maxLength
```
Added value: +1000
```
- addedInput schema / properties / document_type / minLength
```
Added value: +1
```
- addedInput schema / properties / domain / maxLength
```
Added value: +1000
```
- addedInput schema / properties / domain / minLength
```
Added value: +1
```
- addedInput schema / properties / hierarchy / maxLength
```
Added value: +1000
```
- addedInput schema / properties / hierarchy / minLength
```
Added value: +1
```
- addedInput schema / properties / jurisdiction / maxLength
```
Added value: +64
```
- addedInput schema / properties / jurisdiction / minLength
```
Added value: +1
```
- addedInput schema / properties / language / maxLength
```
Added value: +16
```
- addedInput schema / properties / language / minLength
```
Added value: +1
```
- addedInput schema / properties / limit / maximum
```
Added value: +100
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- addedInput schema / properties / offset / maximum
```
Added value: +100000
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
- addedInput schema / properties / publisher / maxLength
```
Added value: +64
```
- addedInput schema / properties / publisher / minLength
```
Added value: +1
```
- addedInput schema / properties / source_class / maxLength
```
Added value: +1000
```
- addedInput schema / properties / source_class / minLength
```
Added value: +1
```

Changed8 schema fields changedAug 7, 2026

addedInput schema / properties / act_form

Added value: +{
+  "description": "optional legal act form",
+  "type": "string"
+}

addedInput schema / properties / binding_status

Added value: +{
+  "description": "optional binding status",
+  "type": "string"
+}

changedInput schema / properties / document_type / description

Previous value: -"optional type code, e.g. CODE"New value: +"backward-compatible source document class filter"

addedInput schema / properties / domain

Added value: +{
+  "description": "optional reviewed legal domain",
+  "type": "string"
+}

addedInput schema / properties / hierarchy

Added value: +{
+  "description": "optional normalized legal hierarchy",
+  "type": "string"
+}

addedInput schema / properties / jurisdiction

Added value: +{
+  "description": "optional jurisdiction code from index metadata, e.g. LU or EU",
+  "type": "string"
+}

addedInput schema / properties / language

Added value: +{
+  "description": "optional language code",
+  "type": "string"
+}

addedInput schema / properties / source_class

Added value: +{
+  "description": "optional source document class",
+  "type": "string"
+}

First observedAug 7, 2026

TDQS

D1.5/5.0

Behavior1/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, yet it does not say whether this is a read-only lookup, what permissions are needed, how pagination works despite the limit parameter, or what the response contains. The vague phrase 'works with' provides essentially no behavioral transparency.

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

Conciseness2/5

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

It is a single short sentence, but it is not concise in a useful way: it is under-specified, awkwardly worded, and does not front-load what the tool actually does. The brevity reflects missing information rather than efficient structure.

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

Completeness1/5

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

For a tool with five parameters, no annotations, and no output schema, this description is far too thin. It leaves the agent without enough information to invoke the tool correctly or understand its results.

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

Parameters1/5

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

There are five parameters with 0% schema description coverage, and the description only gestures at the required date. It says nothing about limit, language, identifier, or after_work_key, so agents get no semantic guidance for most inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and the phrase 'state applicable on a date' hint that this concerns Luxembourg legal state at a point in time, but the verb 'works with' is vague and the sentence is ungrammatical. It does not state what the tool returns or how it differs from siblings like as_of or status_on.

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?

The description gives no explicit when-to-use guidance, no exclusions, and no alternatives. It only implies that a date is relevant, leaving the agent to infer when this tool should be selected over closely related siblings.

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.

in_force_on

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources