Lex — Temporal Luxembourg and EU Law

changes_in_period

ACROSS the corpus: which works gained new versions between two dates, how many each, and when — the aggregate counterpart of diff/timeline (which cover ONE work). Use for "what changed between 2025 and 2026", "which laws changed most during the pandemic", "what moved last month". order=by_churn ranks by number of new versions; by_date (default) lists most recently changed first.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	default 20
`order`	No	by_date (default) or by_churn
`domain`	No	legacy domain filter; current v4 indexes leave it empty
`offset`	No	skip this many, for paging
`to_date`	Yes	ISO date, end of window (inclusive)
`act_form`	No	optional legal act form
`language`	No	optional language code
`from_date`	Yes	ISO date, start of window (inclusive)
`hierarchy`	No	optional normalized legal hierarchy
`publisher`	No	optional publisher id
`jurisdiction`	No	optional jurisdiction code from index metadata, e.g. LU or EU
`source_class`	No	optional source document class; alias of document_type
`document_type`	No	optional source document class(es), comma-separated; prefix with ! to exclude, e.g. !RECUEIL,!CODE_RECUEIL for instruments only
`binding_status`	No	optional binding status

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

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

A4.6/5.0

Behavior4/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. It discloses the aggregate, read-oriented nature (gaining versions across the corpus) and explains the behavior of the order parameter (by_churn ranks by count, by_date lists recently changed). It does not mention side effects, but the query nature is clear. It adds context beyond the schema, earning a 4.

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?

Three sentences of dense, front-loaded information. The first sentence establishes purpose, the second gives usage examples, and the third clarifies order semantics. Every sentence earns its place; there is no fluff or redundancy.

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

Completeness4/5

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

Given the complexity (14 parameters, no annotations, no output schema), the description provides a strong conceptual overview, usage examples, and key parameter semantics. It doesn't enumerate all filters, but the schema covers them. It lacks explicit return format, but that is not critical for a list-style tool. Overall, it is complete enough for an agent to select and invoke the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. The description adds meaningful semantic value by explaining what each order enum does ('by_churn ranks by number of new versions; by_date lists most recently changed first'), which is not fully expressed in the schema. This pushes it above the baseline.

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: to identify works that gained new versions across the corpus within a date range, including counts and dates. It explicitly distinguishes itself from diff/timeline by calling itself the 'aggregate counterpart' covering multiple works, which is a strong differentiation from siblings.

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

Usage Guidelines5/5

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

The description provides explicit when-to-use guidance with concrete example queries like 'what changed between 2025 and 2026' and 'which laws changed most during the pandemic'. It also implicitly tells when not to use it by noting that diff/timeline cover ONE work, steering users to the appropriate alternative.

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.

changes_in_period

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources