Skip to main content
Glama

justicelibre

by io.github.Dahliyaal
OverviewDiscussionsAdmin

get_law_article

Read-onlyIdempotent

Article of a French code or statute, as in force on a date (default: today). code: abbreviation ("CT", "cc"), name ("code du travail"), LEGITEXT or statute ("loi 91-647", "loi du 1er juillet 1901"); list: about(topic="codes"). European texts: "CEDH" (protocols: num="P1-1"), "CHARTE_UE", "TUE", "TFUE"; treaties: "CIDE", "GENEVE1951", "HAYE1980"… (with French status); EU acts: "RGPD", "directive 93/13", "UE-" (repealed: flagged). To cite an older decision, pass its date: the article is served as it stood then. view="versions": its history; view="map": wordings, citing texts, implementing orders. etat/note flag a lag behind Légifrance; info_numero, a renumbering. num also accepts a LEGIARTI (code may then be omitted). Without num, a LEGITEXT (outside codes), a European text or a treaty gives the whole text, 120 articles per page (suite: offset=…).

Examples: get_law_article(code="CIDE", num="3"); get_law_article(code="code civil", num="1382", date="2015-06-01")

Input Schema

NameRequiredDescriptionDefault
numNoarticle number ("1128", "L1152-1") or "LEGIARTI…"; empty with code="LEGITEXT…" (outside codes) or "CEDH"…: whole text, 120/page.
codeNoabbreviation, code name ("code du travail"), LEGITEXT or statute ("loi 91-647", "loi du 1er juillet 1901"); list: about(topic="codes"); also "CEDH" (protocols: num="P1-1"), "CHARTE_UE", "TUE", "TFUE"; EU secondary law in force: "UE-<CELEX>", "RGPD", "DSA", "directive 93/13".
dateNoISO date YYYY-MM-DD (optional; if absent, the version in force). With the date of a decision, the article is served as it stood on that date.
viewNotext (default: the article) | versions (its successive wordings) | map (texts that created, amended, cite or implement it).text
offsetNowhole text: value of `suite` (120, 240…).
fallback_currentNodate before the first version: false = error `not_in_force_at_date` (`premiere_version`, `ancien_numero`); true = current text flagged `hors_date`.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / num / description
      Previous value: -"article number (\"1128\", \"L1152-1\") or \"LEGIARTI…\"; empty with code=\"LEGITEXT…\" outside the codes: whole text, 120 articles per page."New value: +"article number (\"1128\", \"L1152-1\") or \"LEGIARTI…\"; empty with code=\"LEGITEXT…\" (outside codes) or \"CEDH\"…: whole text, 120/page."
  2. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"abbreviation, code name (\"code du travail\"), LEGITEXT or statute (\"loi 91-647\", \"loi du 1er juillet 1901\"); list: about(topic=\"codes\"); also \"CEDH\" (protocols: num=\"P1-1\"), \"CHARTE_UE\", \"TUE\", \"TFUE\"."New value: +"abbreviation, code name (\"code du travail\"), LEGITEXT or statute (\"loi 91-647\", \"loi du 1er juillet 1901\"); list: about(topic=\"codes\"); also \"CEDH\" (protocols: num=\"P1-1\"), \"CHARTE_UE\", \"TUE\", \"TFUE\"; EU secondary law in force: \"UE-<CELEX>\", \"RGPD\", \"DSA\", \"directive 93/13\"."
  3. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"abbreviation, code name (\"code du travail\"), LEGITEXT or statute (\"loi 91-647\", \"loi du 1er juillet 1901\"); list: about(topic=\"codes\")."New value: +"abbreviation, code name (\"code du travail\"), LEGITEXT or statute (\"loi 91-647\", \"loi du 1er juillet 1901\"); list: about(topic=\"codes\"); also \"CEDH\" (protocols: num=\"P1-1\"), \"CHARTE_UE\", \"TUE\", \"TFUE\"."
  4. Changed1 schema field changed
    • addedInput schema / properties / fallback_current
      Added value: +{
+  "default": false,
+  "description": "date before the first version: false = error `not_in_force_at_date` (`premiere_version`, `ancien_numero`); true = current text flagged `hors_date`.",
+  "title": "Fallback Current",
+  "type": "boolean"
+}
  5. Changed5 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"sigle, nom du code (« code du travail »), LEGITEXT ou texte (« loi 91-647 », « loi du 1er juillet 1901 ») ; liste : about(topic=\"codes\")."New value: +"abbreviation, code name (\"code du travail\"), LEGITEXT or statute (\"loi 91-647\", \"loi du 1er juillet 1901\"); list: about(topic=\"codes\")."
    • changedInput schema / properties / date / description
      Previous value: -"date ISO YYYY-MM-DD (optionnel — si absent, version en vigueur). Avec la date d'une décision, l'article est servi tel qu'il était à cette date."New value: +"ISO date YYYY-MM-DD (optional; if absent, the version in force). With the date of a decision, the article is served as it stood on that date."
    • changedInput schema / properties / num / description
      Previous value: -"numéro de l'article (ex : \"1128\", \"L1152-1\", \"132-1\")"New value: +"article number (\"1128\", \"L1152-1\") or \"LEGIARTI…\"; empty with code=\"LEGITEXT…\" outside the codes: whole text, 120 articles per page."
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "whole text: value of `suite` (120, 240…).",
+  "title": "Offset",
+  "type": "integer"
+}
    • changedInput schema / properties / view / description
      Previous value: -"text (défaut : l'article) | versions (ses rédactions successives) | map (textes qui l'ont créé, modifié, qui le citent ou l'appliquent)."New value: +"text (default: the article) | versions (its successive wordings) | map (texts that created, amended, cite or implement it)."
  6. Changed3 schema fields changed
    • addedInput schema / properties / code / default
      Added value: +""
    • addedInput schema / properties / num / default
      Added value: +""
    • removedInput schema / required
      Removed value: -[
-  "code",
-  "num"
-]
  7. Changed2 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"sigle, nom du code (« code du travail »), LEGITEXT ou texte (« loi 91-647 », « loi du 1er juillet 1901 ») ; liste : resource `justicelibre://codes-supportes`."New value: +"sigle, nom du code (« code du travail »), LEGITEXT ou texte (« loi 91-647 », « loi du 1er juillet 1901 ») ; liste : about(topic=\"codes\")."
    • changedInput schema / properties / date / description
      Previous value: -"date ISO YYYY-MM-DD (optionnel — si absent, version en vigueur). Utiliser la date de la décision citante pour obtenir la version contemporaine de la citation."New value: +"date ISO YYYY-MM-DD (optionnel — si absent, version en vigueur). Avec la date d'une décision, l'article est servi tel qu'il était à cette date."
  8. Changed1 schema field changed
    • addedInput schema / properties / view
      Added value: +{
+  "default": "text",
+  "description": "text (défaut : l'article) | versions (ses rédactions successives) | map (textes qui l'ont créé, modifié, qui le citent ou l'appliquent).",
+  "title": "View",
+  "type": "string"
+}
  9. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"code court (ex : \"CC\" pour Code civil, \"CT\" pour Code du travail)"New value: +"sigle, nom du code (« code du travail »), LEGITEXT ou texte (« loi 91-647 », « loi du 1er juillet 1901 ») ; liste : resource `justicelibre://codes-supportes`."
  10. Changed3 schema fields changed
    • addedInput schema / properties / code / description
      Added value: +"code court (ex : \"CC\" pour Code civil, \"CT\" pour Code du travail)"
    • addedInput schema / properties / date / description
      Added value: +"date ISO YYYY-MM-DD (optionnel — si absent, version en vigueur). Utiliser la date de la décision citante pour obtenir la version contemporaine de la citation."
    • addedInput schema / properties / num / description
      Added value: +"numéro de l'article (ex : \"1128\", \"L1152-1\", \"132-1\")"
  11. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description layers on genuinely additive behavior: the `not_in_force_at_date` error with `premiere_version`/`ancien_numero`, the `hors_date` flag when fallback_current is used, the 120-articles-per-page pagination via `suite`, and the `etat`/`note`/`info_numero` flags signalling Légifrance lag and renumbering. This is the kind of edge-case disclosure annotations cannot carry.

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

Conciseness4/5

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

The core purpose is front-loaded and every sentence carries information — nothing is filler. It is nonetheless a dense wall of parentheticals and semicolon-chained clauses that is harder to scan than it needs to be, and the two trailing examples could be trimmed.

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?

With an output schema present, return values need no explanation, and 100% schema coverage plus rich annotations leave little structural burden on the description. It covers namespaces, date semantics, views, pagination and error modes thoroughly; the remaining gap is sibling disambiguation, which is the one thing an agent still has to guess.

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% and the schema text is itself highly detailed, so the baseline is 3. The prose largely restates the same parameter semantics (code formats, view values, offset as a `suite` value, fallback_current behavior); the only mildly additive element is the worked example showing num plus date for citing an old decision.

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 opens with a precise verb+resource statement: an article of a French code or statute, as in force on a given date. It goes further by enumerating the accepted code namespaces (codes, LEGITEXT, statutes, European texts, treaties, EU acts). It never names or contrasts a sibling, however, so an agent must infer the boundary with search_legislation or get_legislative_history on its own.

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?

It gives concrete routing context inside the tool: how to discover code abbreviations (about(topic="codes")), that omitting num yields the whole text, that view="versions"/"map" switch to history or citation graphs, and that passing a decision's date serves the article as it then stood. What is missing is explicit when-not guidance — nothing says when to prefer search_legislation or the separate get_legislative_history tool over view="versions".

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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