Lex — Temporal Luxembourg and EU Law

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. Dates show when Glama detected each change.

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

A4.5/5.0

Behavior5/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It reveals the computation method (timeline intervals), deduplication by work, and the output contract (timeline_semantics in the envelope, mandatory population disclosure), going well beyond the schema.

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

Conciseness5/5

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

Two sentences are packed with essential information: the core purpose, the key semantic distinction, and the output characteristics. No unnecessary words; the structure front-loads the main purpose and then adds critical caveats.

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

Completeness5/5

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

Given 12 parameters, no output schema, and no annotations, this description is remarkably complete. It explains what the tool computes, the crucial distinction from entry into force, the deduplication logic, and key aspects of the response envelope, enabling an agent to use it 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?

Schema description coverage is 100% with each parameter already having a description, so the baseline is 3. The description adds high-level semantics about publisher states and date coverage but does not elaborate on parameter-specific behavior or interactions beyond what the schema provides.

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 computes publisher states covering a given date from timeline intervals, deduplicated by work. It also explicitly contrasts Legilux applicability states with EUR-Lex official consolidated wording states, making it unmistakable that this is not an entry-into-force tool.

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

Usage Guidelines4/5

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

Provides contextual guidance by clarifying the difference between Legilux and EUR-Lex states and warning against mislabeling the result as 'entry into force.' However, it doesn't explicitly name alternative sibling tools or state when to prefer them, so it's not fully explicit.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but timeline and article_history both cover historical versions, and as_of and in_force_on both relate to state on a date. Descriptions are detailed enough to resolve overlap, so confusion is limited.

Naming Consistency3/5

All names are lowercase with underscores, but they mix noun forms (coverage, provenance), verb forms (search, diff), and prepositional phrases (as_of, in_force_on, changes_in_period). This is readable but lacks a consistent pattern like verb_noun.

Tool Count5/5

Ten tools is well within the ideal range for a specialized legal research server. Each tool addresses a distinct aspect of temporal legal queries, and none feel redundant or superfluous.

Completeness5/5

The tool set covers search, retrieval, history, citations, coverage gaps, and provenance. It supports both document-level and corpus-level temporal analysis, making it comprehensive for the stated domain of Luxembourg and EU law research.

in_force_on

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources