Skip to main content
Glama

Lex: Luxembourg Law MCP Server

by lu.soufien.law
OverviewDiscussionsAdmin

as_of

The state of one document as it stood on one date. Pure lookup, no ranking. mode=outline lists provisions without text and may be narrowed with anchors; mode=select returns only the named anchors' text; mode=full (default) returns the whole text. Every provision carries its own permalink and hash.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesISO date YYYY-MM-DD
modeNofull | outline | select (default full)
workYesWork-level lex_id (publisher:workkey), version-level lex_id (version segment ignored), or verbatim publisher identifier with publisher supplied. Unknown document -> call search first.
anchorsNooptional comma-separated provision anchors for mode=outline; required for mode=select, e.g. art_1er,art_33
languageNooptional language code, e.g. fr
publisherNopublisher id; required when work is not publisher-qualified
version_keyNooptional opaque key returned by timeline or an ambiguous_version choice

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / allOf
      Added value: +[
+  {
+    "if": {
+      "properties": {
+        "mode": {
+          "const": "select"
+        }
+      },
+      "required": [
+        "mode"
+      ]
+    },
+    "then": {
+      "required": [
+        "anchors"
+      ]
+    }
+  }
+]
    • 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])$"
    • addedInput schema / properties / version_key
      Added value: +{
+  "description": "optional opaque key returned by timeline or an ambiguous_version choice",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed15 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / anchors / maxLength
      Added value: +1000
    • addedInput schema / properties / anchors / 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 / language / maxLength
      Added value: +16
    • addedInput schema / properties / language / minLength
      Added value: +1
    • addedInput schema / properties / mode / enum
      Added value: +[
+  "full",
+  "outline",
+  "select"
+]
    • addedInput schema / properties / mode / maxLength
      Added value: +64
    • addedInput schema / properties / mode / 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"
+}
    • 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
  3. Changed1 schema field changed
    • changedInput schema / properties / anchors / description
      Previous value: -"comma-separated provision anchors for mode=select, e.g. art_1er,art_33"New value: +"optional comma-separated provision anchors for mode=outline; required for mode=select, e.g. art_1er,art_33"
  4. First observed

TDQS

A4.4/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 that the tool is a pure lookup with no ranking, explains the behavior of each mode (outline, select, full), the default mode, and mentions that every provision carries a permalink and hash. It lacks error-handling and authorization details, but for a read-only lookup this is transparent enough.

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?

The description is two sentences long and tightly packed with essential information. It front-loads the core purpose, then efficiently explains modes and output characteristics without any filler.

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?

There is no output schema, but the description explains what is returned in each mode (whole text, outline, selected anchors' text) and notes the permalink/hash. It covers the main usage scenarios and parameter behavior, though error cases or special conditions are not mentioned. For a lookup tool with full schema coverage, this is sufficiently complete.

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 the baseline is 3. The description adds significant meaning beyond the schema by explaining the semantics of 'mode' and 'anchors' (e.g., what outline vs. select returns, how anchors narrow results), which is not fully captured in the schema descriptions.

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 states the tool returns 'the state of one document as it stood on one date', which is a specific verb (lookup) and resource (document at a date). It also distinguishes from search/ranking by explicitly saying 'Pure lookup, no ranking.' This clearly differentiates it from sibling tools like search 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 Guidelines4/5

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

The description provides clear context for when to use the tool (historical document snapshot) and explains the different modes and anchoring, which guides usage. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of a full 5.

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 toolsInspect
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