Skip to main content
Glama

Lexou · droit français

Lire un article de loi en vigueur

lire_article_de_loi
Read-onlyIdempotent

Texte intégral d'un article en vigueur d'un code ou d'une loi, lu dans la copie de Légifrance tenue par Lexou, avec son lien officiel et sa date d'entrée en vigueur. À utiliser quand on connaît le numéro et le texte (« 1240 », « Code civil » ; « L1237-13 », « Code du travail » ; « 22 », « Loi n° 89-462 du 6 juillet 1989 »). Pas pour chercher un article par thème, ni pour une version passée.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "numero": "<numero>",
      "texte": "<texte>"
    },
    "name": "lire_article_de_loi"
  }
}

Input Schema

NameRequiredDescriptionDefault
texteYesNom exact du code ou du texte, par exemple « Code civil », « Code de l'urbanisme », « Loi n° 89-462 du 6 juillet 1989 »
numeroYesNuméro de l'article, par exemple 1240, L1237-13, R421-17

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond them: results come from Lexou's own Légifrance copy and are restricted to the currently in-force version, plus it names the return fields (link, entry-into-force date). It stops short of describing not-found behavior or how stale the local copy may be.

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, zero filler: what it returns, when to call it, when not to. The output content and the usage precondition are front-loaded before the exclusions.

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

Completeness5/5

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

For a two-parameter read-only lookup with no output schema, the description covers what is returned (full text, official link, entry-into-force date), the source of truth, and the version constraint. Nothing an agent needs in order to call it correctly is missing.

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 already documents both fields with examples and length bounds. The description adds the value of pairing specific numbers with specific texts ('1240' + 'Code civil'), which reinforces that the two parameters must be matched, but it introduces no format or syntax detail the schema lacks. Baseline 3 applies.

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 a specific verb and resource (full text of an in-force article from a code or law), names the data source (Lexou's copy of Légifrance) and the returned artifacts (official link, entry-into-force date). An agent can immediately tell this is a direct-lookup tool rather than any of the calculator or service-lookup 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?

It gives an explicit precondition ('À utiliser quand on connaît le numéro et le texte') backed by three concrete number/text pairings, and two explicit exclusions: not for thematic search, not for past versions. That is the when/when-not/alternative triad in compact form.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources