Lex: Luxembourg Law MCP Server

diff

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

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "identifier": "<identifier>",
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "diff"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedNov 2, 2026

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

addedInput schema / properties / page

Added value: +{
+  "maximum": 100000,
+  "minimum": 1,
+  "type": "integer"
+}

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"
+]

Changed4 schema fields changedAug 17, 2026

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

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

Changed1 schema field changedAug 9, 2026

addedInput schema / properties / anchor

Added value: +{
+  "description": "optional held provision anchor returned by search, e.g. art_92",
+  "type": "string"
+}

First observedAug 5, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations and no output schema, the description carries the full behavioral burden. It says nothing about what the diff returns (e.g., changed articles, text deltas), pagination behavior implied by the page parameter, or any auth/rate-limit considerations.

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 a single, front-loaded sentence with no wasted words. Its brevity is appropriate, though the phrase 'states of a Luxembourg act' could be slightly clearer.

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 five-parameter tool with no annotations and no output schema, the description is too thin. It omits return format, pagination, language semantics, and how the two dates are interpreted, leaving significant gaps for an agent to call it correctly.

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%, so the description must compensate for five undocumented parameters. It loosely implies identifier refers to a Luxembourg act and date_from/date_to are the comparison dates, but it says nothing about language or page, leaving most parameter meaning unexplained.

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 states a specific operation (article-level difference) on a specific resource (states of a Luxembourg act) across two dates. It is clearer than a generic 'diff', but it does not distinguish itself from similar siblings such as changes_in_period 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 Guidelines2/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 like changes_in_period, timeline, or article_history. The description gives no preconditions, exclusions, or routing hints for the agent.

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?