LibreJustice

View saved version →

---
name: recherche-jurisprudence
description: Search and cite French and European case law with the LibreJustice MCP tools. Use whenever the user asks about court decisions (Cour de cassation, Conseil d'État, cours d'appel, TJ/TA, CNDA, Conseil constitutionnel, CNIL, CEDH, CJUE), needs authorities for a brief, requête, référé or consultation, wants to check how courts rule on an issue, or needs counts of decisions on a point, even if they never mention LibreJustice.
---

# French and European case-law research (LibreJustice)

The user needs decisions whose reasoning states a precise proposition, applicable to the situation at hand, with a quotable excerpt.

The tools come from the LibreJustice MCP server; if `search_decisions` is missing from your session, connect it first: [references/install-mcp.md](references/install-mcp.md).

Five rules dominate everything:

1. **No decision appears in the answer (as support, contrary authority, analogy, or lead) unless you read its full text with `get_decision`.** An `aiSummary` or a `snippet` is not reading.
2. **Quotation marks quote a text you fetched, nothing else.** A hit's `aiSummary` is a machine paraphrase, never the court's words; a `snippet` is verbatim but torn from context. Every quoted string in the answer is copied character-for-character from a `get_decision` or `get_norm` text of this session: not opened means not quotable. A quotation is **one continuous span of one single text**, cuts marked « […] » : merging passages, or decisions, into one pair of quotation marks is fabrication, one source per quote, two passages are two quotes. A sentence reporting a decision in your own voice (« la cour retient que… » followed by your summary or a parenthesized list) is prose, never a quotation.
3. **Every decision named anywhere is a markdown link** to its `url` verbatim: `[CA Paris, 10 janv. 2024, n° 21/22203](https://librejustice.fr/decision/…)`. Never reconstruct or shorten a URL.
4. **The exact object of the question is a hard filter.** The most quotable sentence in the corpus routinely concerns a near-twin object one word apart: another mention, another délai, another clause. A decision whose decisive sentence names a different object is an analogy, never an authority. When the decisive sentence leaves the object unqualified (« l'heure », « ce délai », « cette mention »), its object is the one in the moyen it answers: find the party critique above it; the sentence inherits *that* object.
5. **The first and last lines of every `get_decision` text are the decision's fate on appeal.** A `[SORT DE CETTE DÉCISION SUR RECOURS : …]` banner (also served as the `appellateFate` field) states what became of it on review. Copy it into the answer. It overrides your own docket sweep: a sweep that found nothing while the text carries a banner means the sweep missed the arrêt, never that none exists.

A `get_decision` response may also carry `commentaires`, the court's own analysis served inline (`body`) and outbound links (`url`) to the rapporteur public's conclusions or related court documents. They are context and cite as commentary, never as the ruling: only the decision text quotes as the court's words.

## Protocol: run the steps in order

### 1. Frame

Pin down (ask when the request leaves them open): the proposition in one sentence; who demands what and what winning means; the legally relevant date; the target courts; the exclusions; the proximity axes that decide transposability. **A legal assertion inside the question (« c'est bien uniquement devant telle juridiction ? », « cet acte est nul, non ? ») is a claim to research, never an input**: the complement of the assertion gets its own step-2 sweeps (its own queries and filters, including the courts or outcomes the assertion excludes), and the answer's opening sentence states your verified verdict, never an echo of the premise. Follow-ups refine, they never reset: « d'autres ? » = new decisions, same bar; « tu peux vérifier ? » = re

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.

View saved version →

---
name: recherche-normes
description: Find and quote legal texts and administrative guidance with the LibreJustice MCP tools, covering French codes at any date, EU law, treaties and bilateral accords, foreign codes (59 countries), collective agreements, BOFiP and circulaires. Use whenever the user asks what a text says or said at a given date, which version or which text applies to a situation, needs the exact wording of a provision for a brief, or works with foreign or international law in French litigation, even if they never mention LibreJustice.
---

# Statutory research (LibreJustice)

The user needs the exact provision, in the version in force at the legally relevant date, linked and quoted verbatim. A paraphrase from memory is not a deliverable: models misremember article numbers and miss amendments; every quoted provision comes from `get_norm`.

The referential goes far beyond French codes: EU law, international treaties (including bilateral accords), the codes of 59 foreign countries, collective agreements, BOFiP. Map and counts: [references/corpus.md](references/corpus.md). Observed failure modes: [references/traps.md](references/traps.md). Foreign and international law: [references/foreign-law.md](references/foreign-law.md).

The tools come from the LibreJustice MCP server; if `get_norm` is missing from your session, connect it first: [references/install-mcp.md](references/install-mcp.md).

## Iron rules

1. **Never quote a provision from memory.** Fetch it with `get_norm`, quote verbatim, link the article (`[Article 7 bis de l'Accord franco-algérien du 27 décembre 1968](https://librejustice.fr/norm/…)`, the `url` verbatim).
2. **Date before text.** Identify the legally relevant date first (the attacked decision, the facts, the contract), pass it as `date` (both `get_norm` and `search_norms` take it; the search then matches the versions valid at that date), and say which version you quote (its validity window is in the response). The version in force today is the wrong one for most litigation.
3. **Name texts by their official name.** The `code` filter resolves slugs and exact official names, not usual names: « CEDH » and « Convention européenne des droits de l'homme » fail where « Convention de sauvegarde des droits de l'homme et des libertés fondamentales » works. When unsure, recover the slug from `facets.code` or from an inline `/norm/` link in a decision.

A `get_norm` response may also carry `commentaires`, doctrine anchored on the article, served inline (`body`) or as outbound links (`url`). Context, never the norm: only the article text quotes as the provision.

## Three access paths, cheapest first

1. **Text and article known**: compose the URL directly, `https://librejustice.fr/norm/{juris}/{code-slug}/{article-key}` (`fr/code-civil`/`47`, `sn/code-de-la-famille`/`40`, `intl/accord-franco-algerien-du-27-decembre-1968`/`7-bis`; `{juris}` is the enacting jurisdiction in lowercase, `fr`, `eu`, `intl` or an ISO country code; keys are lowercase, `l761-1` for L. 761-1). A wrong slug errors back with the closest ones: guessing then correcting is one call, a search is two. The root `/norm/{juris}/{code-slug}`, with no key, always answers and never carries `num`: a text with no articles (circulaire, publication decree) comes back whole, one with articles comes back as its table of contents in `articles`, bodies joined when the text is short. On a text you do not know, read the root first. **To read a chapter, fetch the division, not its articles.** Table of contents entries with `kind: "section"` carry the url of the division, the path of its segments (`/norm/fr/code-civil/livre-i/titre-v`), that `get_norm` takes: it returns every article of that division with its body, where walking them one by one costs one call each. Past the inline reading budget the bodies drop out, `omitted` says how many, and each entry `url` still fetches its own article. An article carries its `section` too, the division enclosing it: i

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 6 — file references are metadata, not package contents.