Skip to main content
Glama

Lex — Temporal Luxembourg and EU Law

by io.github.SFHAJJI
OverviewDiscussionsAdmin

timeline

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.

Input Schema

NameRequiredDescriptionDefault
languageNo
identifierYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / identifier
      Added value: +{
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}
    • addedInput schema / properties / language
      Added value: +{
+  "minLength": 1,
+  "pattern": "\\S",
+  "type": "string"
+}
    • removedInput schema / properties / limit
      Removed value: -{
-  "description": "max versions (default 100)",
-  "maximum": 200,
-  "minimum": 1,
-  "type": "integer"
-}
    • removedInput schema / properties / offset
      Removed value: -{
-  "description": "pagination offset",
-  "maximum": 100000,
-  "minimum": 0,
-  "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 / 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"
-]New value: +[
+  "identifier"
+]
  2. Changed9 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • 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
      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. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description still discloses meaningful behavior: it returns every state or wording and specifies ordering by publisher applicability or wording date. However, it does not state whether the operation is read-only, how results are structured, or whether pagination or permissions apply.

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 definition is a single dense sentence with no wasted words, and the core output is front-loaded. The semicolon cleanly separates the Luxembourg and EU act cases.

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?

There are no annotations and no output schema, and both parameters lack schema descriptions. The description explains output scope and ordering but leaves invocation-critical details such as identifier format, language behavior, and result structure unaddressed.

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 explain the parameters, but it does not. The required identifier is only indirectly implied to identify a Luxembourg or EU act, and the optional language parameter is not addressed at all.

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 clearly identifies the resource: a timeline of every state of a Luxembourg act or every wording of an EU act, with ordering rules. It distinguishes jurisdiction-dependent behavior, though it does not explicitly differentiate itself from siblings such as article_history, as_of, or events.

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?

The description gives no explicit guidance on when to use this tool instead of alternatives like article_history, as_of, in_force_on, or events. The implied usage is to retrieve a full timeline, but no conditions or exclusions are stated.

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