Skip to main content
Glama

Lex — Temporal Luxembourg and EU Law

Server Details

Temporal search and comparison for official Luxembourg and reviewed EU law, with provenance.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
SFHAJJI/lex
GitHub Stars
9
Server Listing
Lex: Luxembourg Law MCP Server
ChatGPT
–
Claude
–

TDQS

C2.3/5.0

Scored across 27 tools

Disambiguation3/5

Several clusters overlap heavily: as_of vs as_observed vs status_on vs in_force_on all answer 'state on a date' questions, and citation vs cited_by vs relations, plus dossier vs classification vs manifestation vs provenance, differ only in framing. The unusually long descriptions do spell out the exact contract and refusals, which rescues the set, but an agent picking between as_of and as_observed or between dossier and classification will often guess wrong.

Naming Consistency3/5

Casing is uniformly snake_case, which is good, but the convention mixes verb phrases (resolve, verify, browse, search), bare nouns (dossier, classification, provenance, manifestation), prepositional temporals (as_of, as_observed, in_force_on, status_on), and noun_phrase composites (evidence_bundle, answer_drift, changes_in_period). Readable, but no single predictable pattern an agent can extrapolate.

Tool Count2/5

At 27 tools this is heavy for a read-only legal-data server, and the count is inflated by three refusal-only stubs (concepts, knowable_on, transposition) that return a fixed retrieval_mode_unavailable and could be folded into coverage or a single capability-query tool. The remaining surface is dense enough that tool selection itself becomes a task.

Completeness3/5

The read-only lifecycle for held Luxembourg acts is well covered (browse, search, resolve, timeline, as_of, diff, citation/cited_by, provenance, verify, evidence_bundle), and read-only is appropriate for the domain. However, declared gaps are significant for an EU-law research server: transposition links, EuroVoc concepts, and knowable_on are all unimplemented, and EU-act coverage beyond a single named work looks thin.

Available Tools

27 tools
answer_driftCInspect

The past dated answers a publisher revision invalidated, enumerated from the log's revising events; a genesis log holds none, and the answer says why rather than asserting that nothing drifted.

Inputs: after, limit, identifier.

article_historyCInspect

The history of one article of a Luxembourg act across its states.

Inputs: anchor (required), identifier (required), language.

askCInspect

The assistant, switched on as a labelled preview: the question, with obvious identifiers masked by code, is sent to the configured processor, which only plans which operations to run; code runs them, decides the verdict and writes every sentence from fixed wording; the answer is an answer_dossier (or the refusal advice_boundary), and a question it cannot answer gets assistant_v3_unavailable.

Inputs: question (required).

as_observedCInspect

The state of a Luxembourg act applicable on a date (publisher) as one build of the mounted log held it, named by that build's index digest, with its build time as an upper bound on observation; a time refuses, since no observation time is held.

Inputs: date (required), identifier (required), at, language, +1 more.

as_ofCInspect

The state of a Luxembourg act applicable on a date (publisher), with its articles; for an EU act, the wording dated at or before the date (an EU wording date, never an applicability date).

Inputs: date (required), identifier (required), language.

browseCInspect

The Luxembourg works this mount holds, one ordered and paged list with their identifiers, languages, state dates and the publisher's document types; filter by type or language.

Inputs: type, after, limit, language.

changes_in_periodDInspect

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

Inputs: date_to (required), date_from (required), limit, language, +1 more.

citationDInspect

The references the publisher wrote in the text of a Luxembourg state's articles.

Inputs: date (required), identifier (required), after, limit, +2 more.

cited_byCInspect

The references, in any held Luxembourg state, whose target is exactly this work.

Inputs: identifier (required), after, limit.

classificationCInspect

The publisher's typed facts about a Luxembourg work, verbatim: document type, RDF types, legal value, responsible body, historical identifiers, publication and document dates.

Inputs: identifier (required), language.

conceptsAInspect

Not served: the EuroVoc descriptors, directory codes and subject matters of EU works, which no index holds; every call answers the typed refusal retrieval_mode_unavailable, naming the modes this server serves and the data that would serve it.

coverageCInspect

What this mount holds and serves, named, and what it does not.

Inputs: language.

diffCInspect

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

Inputs: date_to (required), date_from (required), identifier (required), page, +1 more.

dossierCInspect

The work record of a Luxembourg act as the index holds it; for an EU work named by identifier, its held expressions from the EU index.

Inputs: identifier (required), language.

eventsCInspect

The Luxembourg event log, polled by cursor, at least once: a genesis log holds one first_sighting per held state; a chained log adds each later build's comparison events; each build's time, never an observation time.

Inputs: after, event, limit.

evidence_bundleCInspect

What a quote of a Luxembourg state needs, one bounded page at a time (at most 50 articles and 96 KiB of text; page or article chooses the page, contents adds the table of contents): each article's text with its digests, the state's permalink, digests, sources and official identities, composed under the rights rule; for an EU act, the same for the wording of the date.

Inputs: date (required), identifier (required), page, article, +2 more.

in_force_onDInspect

The Luxembourg works with a state applicable on a date.

Inputs: date (required), limit, language, identifier, +1 more.

knowable_onBInspect

Not served: what a reader could have known on a date, from publication and observation times, which no build records; every call answers the typed refusal retrieval_mode_unavailable, naming the modes this server serves (as_of, as_observed) and the data that would serve it.

manifestationDInspect

The publisher's manifestations of a Luxembourg work's expressions with their formats and items, the retained one marked with its body digest.

Inputs: identifier (required), format, language.

provenanceCInspect

The retained sources, rule profiles and digests behind a Luxembourg state.

Inputs: date (required), identifier (required), language.

relationsBInspect

The reference edges of a Luxembourg work in both directions, as one ordered, paged list.

Inputs: identifier (required), date, after, limit, +2 more.

resolveBInspect

Resolve a Luxembourg legal-act identifier or a hash-pinned permalink to the work and expression it names.

Inputs: identifier (required).

status_onCInspect

The publisher's force assertions about a Luxembourg work (its inForceStatus, dateEntryInForce and dateNoLongerInForce facts), verbatim, beside the state applicable on a date, with one fixed reading of the dates.

Inputs: date (required), identifier (required), language.

timelineBInspect

Every state of a Luxembourg act the index holds, in publisher applicability order; for an EU act, every wording its census discovered, in wording-date order.

Inputs: identifier (required), language.

transpositionAInspect

Not served: the transposition links between EU directives and Luxembourg measures, which are not acquired; every call answers the typed refusal retrieval_mode_unavailable, naming the modes this server serves (citation, cited_by, relations) and the data that would serve it.

verifyCInspect

Verify a hash-pinned permalink against the state digest the index holds, or read the current digests to pin.

Inputs: identifier (required), language.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.