Lex: Luxembourg Law MCP Server

in_force_on

Compatibility name for publisher states covering a date, computed from timeline intervals and deduplicated by work. Legilux states describe applicability; EUR-Lex states are official consolidated wording states and must not be called entry into force. Every envelope carries timeline_semantics and the result carries a mandatory population disclosure.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	Yes	ISO date
`limit`	No	default 50
`domain`	No	legacy domain filter; current v4 indexes leave it empty
`offset`	No	pagination offset
`act_form`	No	optional legal act form
`language`	No	optional language code
`hierarchy`	No	optional normalized legal hierarchy
`publisher`	No	optional publisher id, e.g. lu-legilux
`jurisdiction`	No	optional jurisdiction code from index metadata, e.g. LU or EU
`source_class`	No	optional source document class
`document_type`	No	backward-compatible source document class filter
`binding_status`	No	optional binding status

Schema Changelog

Changes observed during successful MCP inspections.

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 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses computation from timeline intervals, deduplication by work, envelope timeline_semantics, and a mandatory population disclosure in the result. This adds valuable behavioral context, though it omits potential error conditions or rate limits.

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?

The description is concise but dense, packing important behavior into two sentences. While a bit jargon-heavy (e.g., 'timeline_semantics', 'population disclosure'), it is structured efficiently and front-loads the primary purpose.

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

Completeness3/5

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

The tool has 12 parameters and no output schema, so the description should compensate by explaining result shape more fully. It mentions envelope and population disclosure but does not detail response structure, error scenarios, or examples. The description is useful but incomplete for an agent expected to invoke this correctly.

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

Parameters3/5

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

The input schema provides 100% coverage with descriptions for all parameters. The tool description does not add parameter-level meaning beyond what the schema already states, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool's purpose: returning publisher states covering a date, computed from timeline intervals and deduplicated by work. It also distinguishes key nuances (Legilux vs EUR-Lex), which helps differentiate it from related operations like as_of or timeline.

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

Usage Guidelines3/5

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

The description gives some usage context (e.g., EUR-Lex states must not be called entry into force) but does not explicitly state when to use this tool over siblings like as_of or coverage. Alternatives are not named or contrasted, leaving the agent to infer use cases.

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

All Lex: Luxembourg Law MCP Server 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.

Resources

Need Help?