Lex — Temporal Luxembourg and EU Law

changes_in_period

The Luxembourg states that began in a period, for a work or across the index.

Input Schema

Name	Required	Description	Default
`limit`	No
`date_to`	Yes
`language`	No
`date_from`	Yes
`identifier`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedOct 27, 2026

removedInput schema / properties / act_form

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

removedInput schema / properties / binding_status

Removed value: -{
-  "description": "optional binding status",
-  "maxLength": 1000,
-  "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 / document_type

Removed value: -{
-  "description": "optional source document class(es), comma-separated; prefix with ! to exclude, e.g. !RECUEIL,!CODE_RECUEIL for instruments only",
-  "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 / from_date

Removed value: -{
-  "description": "ISO date, start of window (inclusive)",
-  "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 / 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 20"
```
changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +200
```

removedInput schema / properties / offset

Removed value: -{
-  "description": "skip this many, for paging",
-  "maximum": 100000,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / order

Removed value: -{
-  "description": "by_date (default) or by_churn",
-  "enum": [
-    "by_date",
-    "by_churn"
-  ],
-  "maxLength": 64,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / publisher

Removed value: -{
-  "description": "optional publisher id",
-  "maxLength": 64,
-  "minLength": 1,
-  "type": "string"
-}

removedInput schema / properties / source_class

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

removedInput schema / properties / to_date

Removed value: -{
-  "description": "ISO date, end of window (inclusive)",
-  "maxLength": 10,
-  "minLength": 1,
-  "pattern": "^\\d{4}-(0[1-9]|1[0-2])-(0[1-9]|[12][0-9]|3[01])$",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "from_date",
-  "to_date"
-]New value: +[
+  "date_from",
+  "date_to"
+]

Changed3 schema fields changedAug 17, 2026

changedInput schema / properties / domain / description

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

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

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

Changed32 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 / 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 / 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 / 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 / order / enum
```
Added value: +[
+  "by_date",
+  "by_churn"
+]
```
- addedInput schema / properties / order / maxLength
```
Added value: +64
```
- addedInput schema / properties / order / minLength
```
Added value: +1
```
- 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
```
- 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}$"
```

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(s), comma-separated; prefix with ! to exclude, e.g. !RECUEIL,!CODE_RECUEIL for instruments only"New value: +"optional source document class(es), comma-separated; prefix with ! to exclude, e.g. !RECUEIL,!CODE_RECUEIL for instruments only"

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; alias of document_type",
+  "type": "string"
+}

First observedAug 7, 2026

TDQS

D1.3/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 burden of behavioral disclosure. It does not say whether this is a read-only operation, what permissions are required, how results are ordered or paginated, or what the response contains.

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?

The description is only one sentence, but it is cryptic and poorly structured rather than efficiently informative. Brevity here reflects under-specification, not conciseness.

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?

This is a five-parameter tool with no output schema and no annotations. The description does not compensate with any usable detail about scope, inputs, behavior, or return values, leaving the agent unable to invoke it confidently.

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?

Schema description coverage is 0% for five parameters. The description vaguely references a period and 'a work or across the index', but it does not explain date_from/date_to, identifier, language, or limit, nor does it map any parameter to its purpose.

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 description gestures at a resource ('Luxembourg states') and a temporal scope ('began in a period'), but the phrasing is vague and grammatically unclear. It does not state a specific verb or clearly distinguish this tool from siblings like timeline, as_of, or in_force_on.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives such as timeline, as_of, status_on, or article_history. The description does not mention prerequisites, exclusions, or selection criteria.

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.

changes_in_period

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources