Skip to main content
Glama

Get Decision

get_decision
Read-onlyIdempotent

Fetch the full text and metadata of a decision by its url. The text carries inline markdown links to cited articles (/texte/, open with get_legal_text) and cited decisions (/decision/, open with get_decision); a citation spanning several articles (« articles 3 à 6 », « et suivants ») links its first article and appends the others as labelled links right after the span. appellateFate states in one line what became of THIS decision on review (INFIRMATION = reversed, it no longer stands; CONFIRMATION = upheld): read it before citing the decision as authority. caseChronology lists the prior AND subsequent decisions of the same case (appeal, pourvoi, renvoi). An absent fate or chronology never proves no recourse exists, only that none is linked in the corpus. commentaires carries the institutional commentary (official analyses inline, links to the rapporteur public's conclusions and related court documents): context, never the ruling, so quote the decision text and not a commentaire.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA librejustice.fr decision URL, from a search_decisions hit or an inline citation link; search_decisions first if you have neither.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYes
seatNo
textYes
titleYes
officeNo
solutionNo
procedureNo
dateLectureNo
legalDomainNo
officialUrlNo
publicationNo
commentairesNo
appellateFateNo
docketNumbersNo
caseChronologyNo
jurisdictionCodeNo
jurisdictionTypeYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changed
    • removedOutput schema / description
      Removed value: -"Metadata fields carry search_decisions filter tokens: each field matches the filter of the same name (jurisdictionType → jurisdiction_type, legalDomain → legal_domain…) and its value passes back verbatim to filter."
    • removedOutput schema / properties / appellateFate / description
      Removed value: -"Fate of THIS decision before the court that reviewed it, precomputed from caseChronology: 'INFIRMATION, Cour d'appel de Paris, 1 juillet 2025 (url)'. INFIRMATION = this decision was reversed and no longer stands; CONFIRMATION = upheld. Absent = no recourse known to the corpus, which never proves the decision is final."
    • removedOutput schema / properties / caseChronology / description
      Removed value: -"Prior and subsequent decisions of the same case (appeal, pourvoi, renvoi), most recent first, current decision included. The fate of a judgment reads in the solution of the decision that reviewed it (INFIRMATION = reversed, CONFIRMATION = upheld). Absent chronology never proves no recourse exists."
    • removedOutput schema / properties / caseChronology / items / properties / linkToNext / description
      Removed value: -"Link nature to the step below (the attacked decision): APPEL_DE | POURVOI_CONTRE | RENVOI_APRES_CASSATION."
    • removedOutput schema / properties / caseChronology / items / properties / url / description
      Removed value: -"Absent when the corpus does not hold that step: it is named by the decision that attacks it, and cannot be opened."
    • removedOutput schema / properties / chamber
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Chamber that heard the case, as \"<court>|<chamber>\", reusable verbatim as the chamber filter."
      -}
    • removedOutput schema / properties / commentaires / description
      Removed value: -"Institutional commentary anchored on this document: court-written analyses served inline (`body`), plus outbound links (`url`) to the rapporteur public's conclusions and to related institutional documents (reports, opinions, press releases). Context, never the ruling itself. Quote the decision text, not a commentaire, as the court's words."
    • changedOutput schema / properties / commentaires / items / properties / access / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "libre",
      +      "abonnes"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / commentaires / items / properties / access / description
      Removed value: -"libre | abonnes"
    • removedOutput schema / properties / commentaires / items / properties / kind / description
      Removed value: -"analyse = official court-written abstract, full content in `body`. conclusions = the rapporteur public's conclusions, `url` only (copyright-protected, existence + official link). note = linked institutional document (report, avocat général's opinion, press release, doctrine note), `url` + `title` + `publisher`."
    • addedOutput schema / properties / commentaires / items / properties / kind / enum
      Added value: +[
      +  "analyse",
      +  "conclusions",
      +  "note"
      +]
    • removedOutput schema / properties / commentaires / items / properties / renvois / description
      Removed value: -"Doctrinal cross-references of the analyse (« Cf. CE, … »)."
    • removedOutput schema / properties / commentaires / items / properties / rubriques / description
      Removed value: -"Official classification headings (analyse)."
    • removedOutput schema / properties / commentaires / items / properties / url / description
      Removed value: -"External link, to hand to the user, not openable by an MCP tool."
    • removedOutput schema / properties / officialUrl / description
      Removed value: -"The decision on its official publisher: legifrance.gouv.fr, courdecassation.fr, opendata.justice-administrative.fr, conseil-constitutionnel.fr, hudoc, eur-lex. Cite this when the deliverable requires the authoritative source; `url` is the LibreJustice page. Absent when the publisher exposes no per-decision permalink."
    • removedOutput schema / properties / publication / description
      Removed value: -"Publication values carried, reusable verbatim as the publication filter."
    • addedOutput schema / properties / seat
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  2. Changed3 schema fields changed
    • changedOutput schema / properties / appellateFate / description
      Previous value: -"Fate of THIS decision before the court that reviewed it, precomputed from caseChronology: 'INFIRMATION — Cour d'appel de Paris, 1 juillet 2025 (url)'. INFIRMATION = this decision was reversed and no longer stands; CONFIRMATION = upheld. Absent = no recourse known to the corpus, which never proves the decision is final."New value: +"Fate of THIS decision before the court that reviewed it, precomputed from caseChronology: 'INFIRMATION, Cour d'appel de Paris, 1 juillet 2025 (url)'. INFIRMATION = this decision was reversed and no longer stands; CONFIRMATION = upheld. Absent = no recourse known to the corpus, which never proves the decision is final."
    • changedOutput schema / properties / commentaires / description
      Previous value: -"Institutional commentary anchored on this document: court-written analyses served inline (`body`), plus outbound links (`url`) to the rapporteur public's conclusions and to related institutional documents (reports, opinions, press releases). Context, never the ruling itself — quote the decision text, not a commentaire, as the court's words."New value: +"Institutional commentary anchored on this document: court-written analyses served inline (`body`), plus outbound links (`url`) to the rapporteur public's conclusions and to related institutional documents (reports, opinions, press releases). Context, never the ruling itself. Quote the decision text, not a commentaire, as the court's words."
    • changedOutput schema / properties / commentaires / items / properties / url / description
      Previous value: -"External link, to hand to the user — not openable by an MCP tool."New value: +"External link, to hand to the user, not openable by an MCP tool."
  3. Changed6 schema fields changed
    • changedOutput schema / properties / caseChronology / description
      Previous value: -"Linked prior and subsequent decisions of the same case (appeal, pourvoi, renvoi), most recent first, current decision included. The fate of a judgment reads in the solution of the decision that reviewed it (INFIRMATION = reversed, CONFIRMATION = upheld). Absent chronology never proves no recourse exists."New value: +"Prior and subsequent decisions of the same case (appeal, pourvoi, renvoi), most recent first, current decision included. The fate of a judgment reads in the solution of the decision that reviewed it (INFIRMATION = reversed, CONFIRMATION = upheld). Absent chronology never proves no recourse exists."
    • addedOutput schema / properties / caseChronology / items / properties / url / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedOutput schema / properties / caseChronology / items / properties / url / default
      Added value: +null
    • addedOutput schema / properties / caseChronology / items / properties / url / description
      Added value: +"Absent when the corpus does not hold that step: it is named by the decision that attacks it, and cannot be opened."
    • removedOutput schema / properties / caseChronology / items / properties / url / type
      Removed value: -"string"
    • changedOutput schema / properties / caseChronology / items / required
      Previous value: -[
      -  "title",
      -  "url",
      -  "current"
      -]New value: +[
      +  "title",
      +  "current"
      +]
  4. Changed1 schema field changed
    • removedOutput schema / properties / matiere
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null
      -}
  5. Changed1 schema field changed
    • changedOutput schema / properties / chamber / description
      Previous value: -"Bench that heard the case, as \"<court>|<bench>\", reusable verbatim as the chamber filter."New value: +"Chamber that heard the case, as \"<court>|<chamber>\", reusable verbatim as the chamber filter."
  6. Changed1 schema field changed
    • changedOutput schema / properties / chamber / description
      Previous value: -"Factual bench key, reusable verbatim as the chamber filter."New value: +"Bench that heard the case, as \"<court>|<bench>\", reusable verbatim as the chamber filter."
  7. Changed6 schema fields changed
    • addedOutput schema / properties / chamber
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Factual bench key, reusable verbatim as the chamber filter."
      +}
    • removedOutput schema / properties / publication / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedOutput schema / properties / publication / default
      Removed value: -null
    • addedOutput schema / properties / publication / description
      Added value: +"Publication values carried, reusable verbatim as the publication filter."
    • addedOutput schema / properties / publication / items
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / publication / type
      Added value: +"array"
  8. Changed2 schema fields changed
    • removedOutput schema / properties / chamber
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null
      -}
    • addedOutput schema / properties / matiere
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
  9. Changed1 schema field changed
    • addedOutput schema / properties / officialUrl
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "The decision on its official publisher: legifrance.gouv.fr, courdecassation.fr, opendata.justice-administrative.fr, conseil-constitutionnel.fr, hudoc, eur-lex. Cite this when the deliverable requires the authoritative source; `url` is the LibreJustice page. Absent when the publisher exposes no per-decision permalink."
      +}
  10. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Decision URL, from search_decisions hits or an inline citation link."New value: +"A librejustice.fr decision URL, from a search_decisions hit or an inline citation link; search_decisions first if you have neither."
  11. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, but the description adds significant behavioral context beyond that: how citation spans are linked, what appellateFate and caseChronology mean, and that commentaires are contextual and must not be quoted as the ruling. No contradiction with annotations.

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 description is dense and somewhat long, but every sentence contributes essential operational or interpretive guidance. It front-loads the core fetch action and then systematically covers link handling, fate semantics, chronology, and commentary caveats. It could be tightened, but it is not padded.

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?

Given the tool has an output schema and only one parameter, the description is complete for an agent to invoke it correctly: it explains the source of the URL, how to choose siblings, and how to interpret the key result fields. Nothing essential is missing for correct selection or invocation.

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?

The schema fully documents the single `url` parameter, so the baseline is 3. The description adds useful meaning by specifying that the URL should be a librejustice.fr decision URL obtained from a search_decisions hit or an inline citation link, which improves an agent's ability to supply the correct value.

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 opens with a specific verb and resource: 'Fetch the full text and metadata of a decision by its `url`.' It clearly distinguishes get_decision from siblings by explaining that inline links to cited articles open with get_legal_text and cited decisions open with get_decision, and it routes URL discovery through search_decisions.

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?

The description explicitly says to call search_decisions first if you have neither a decision URL nor an inline citation link, and it tells the agent which sibling to use for cited articles versus cited decisions. It also warns that an absent appellateFate or caseChronology never proves no recourse exists, which is critical guidance for correct usage.

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.

TDQS

A4.7/5.0
Disambiguation5/5

Each tool targets a distinct resource and action: decisions, legal texts, search over each, and user activity. Even though get_decision and get_legal_text both fetch documents, their domains are clearly separated by name and description.

Naming Consistency5/5

All tool names follow the same snake_case verb_noun pattern: get_*, search_*, list_*. There is no mixing of conventions, vague verbs, or inconsistent casing.

Tool Count5/5

Five tools is well-scoped for a legal research server: search and retrieval for both decisions and legal texts, plus user activity. Every tool fills a clear role without redundancy.

Completeness5/5

The domain is read-oriented legal research, and the set covers both search and retrieval for its two primary object types, with user activity as a useful auxiliary. There are no obvious dead ends or missing core operations.