Skip to main content
Glama

get_decision

Read-onlyIdempotent

Full text of a decision, by id or by numero (+ court). Several decisions with that number: list decisions (ECHR/CJEU: the one judgment is served, the rest in autres_documents). An administrative number alone ("2200433") is refused; CE: see homonymes. Also reads doctrine (cada:…, ddd:…), JORFTEXT and KALIARTI ids.

Examples: get_decision(id="CETATEXT000007641393") get_decision(numero="497566", court="CE") get_decision(numero="23/05688", court_name="CA Douai") # RG get_decision(numero="24-14.641") # Cour de cassation appeal; likewise 2024L02643 (commercial court), 6538/74 (ECHR), C-72/24 (CJEU)

Args: id: id from a search (JURITEXT, CETATEXT, 001-…, CELEX, JORFTEXT…), an ECLI (ECLI:FR:…, ECLI:EU:…, ECLI:CE:ECHR:…) or a judicial/European case number numero: case, appeal (pourvoi), RG, commercial court, ECHR or CJEU number court: CE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CPH | CEDH | CJUE | CNDA court_name: "TA Lyon", "CA Douai" nature: DC, QPC… (CONSTIT, shared number)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoid from a search (JURITEXT, CETATEXT, 001-…, CELEX, JORFTEXT…), an ECLI (ECLI:FR:…, ECLI:EU:…, ECLI:CE:ECHR:…) or a judicial/European case number
courtNoCE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CPH | CEDH | CJUE | CNDA
natureNoDC, QPC… (CONSTIT, shared number)
numeroNocase, appeal (pourvoi), RG, commercial court, ECHR or CJEU number
offsetNolong document (over 100,000 characters, served in pages): value of `pagination.suite`
court_nameNo"TA Lyon", "CA Douai"

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"id from a search (JURITEXT, CETATEXT, 001-…, CELEX, JORFTEXT…) or a judicial/European case number"New value: +"id from a search (JURITEXT, CETATEXT, 001-…, CELEX, JORFTEXT…), an ECLI (ECLI:FR:…, ECLI:EU:…, ECLI:CE:ECHR:…) or a judicial/European case number"
  2. Changed1 schema field changed
    • changedInput schema / properties / court / description
      Previous value: -"CE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CPH | CEDH | CJUE"New value: +"CE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CPH | CEDH | CJUE | CNDA"
  3. Changed6 schema fields changed
    • changedInput schema / properties / court / description
      Previous value: -"CE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CEDH | CJUE"New value: +"CE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CPH | CEDH | CJUE"
    • changedInput schema / properties / court_name / description
      Previous value: -"« TA Lyon », « CA Douai »"New value: +"\"TA Lyon\", \"CA Douai\""
    • changedInput schema / properties / id / description
      Previous value: -"id d'une recherche (JURITEXT, CETATEXT, 001-…, CELEX…) ou numéro judiciaire/européen"New value: +"id from a search (JURITEXT, CETATEXT, 001-…, CELEX, JORFTEXT…) or a judicial/European case number"
    • changedInput schema / properties / nature / description
      Previous value: -"DC, QPC… (CONSTIT)"New value: +"DC, QPC… (CONSTIT, shared number)"
    • changedInput schema / properties / numero / description
      Previous value: -"n° de requête, pourvoi, RG, requête CEDH, affaire CJUE"New value: +"case, appeal (pourvoi), RG, commercial court, ECHR or CJEU number"
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "long document (over 100,000 characters, served in pages): value of `pagination.suite`",
      +  "title": "Offset",
      +  "type": "integer"
      +}
  4. Changed5 schema fields changed
    • changedInput schema / properties / court / description
      Previous value: -"CE | CAA | TA | CONSTIT"New value: +"CE | CAA | TA | CONSTIT | CASS | CA | TJ | TCOM | CEDH | CJUE"
    • changedInput schema / properties / court_name / description
      Previous value: -"« TA Lyon », « CAA Douai »"New value: +"« TA Lyon », « CA Douai »"
    • changedInput schema / properties / id / description
      Previous value: -"JURITEXT, CONSTEXT, id Judilibre, CETATEXT, DCE_/DTA_/DCAA_, /Ariane_Web/…, 001-… (CEDH), CELEX (CJUE), cada:… (doctrine)"New value: +"id d'une recherche (JURITEXT, CETATEXT, 001-…, CELEX…) ou numéro judiciaire/européen"
    • changedInput schema / properties / nature / description
      Previous value: -"DC, QPC… (CONSTIT, numéro partagé)"New value: +"DC, QPC… (CONSTIT)"
    • changedInput schema / properties / numero / description
      Previous value: -"n° de requête ou de décision (avec court)"New value: +"n° de requête, pourvoi, RG, requête CEDH, affaire CJUE"
  5. Changed1 schema field changed
    • removedInput schema / properties / session_token
      Removed value: -{
      -  "default": "",
      -  "description": "jeton PISTE (facultatif)",
      -  "title": "Session Token",
      -  "type": "string"
      -}
  6. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is covered. The description goes beyond them by disclosing how multiple matches are served (ECHR/CJEU: one judgment returned, the rest in `autres_documents`) and which inputs are rejected, which is exactly the kind of response-shaping behavior an agent needs. Pagination is only implied by the schema's offset field, not explained here.

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

Conciseness3/5

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

The first line and the examples earn their place, but the 'Args:' section duplicates the input schema field-for-field at 100% coverage, adding length without new information. Line-wrapped fragments ('likewise / 2024L02643…') make the document slightly harder to scan than necessary.

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?

For a read-only lookup tool with an output schema and full schema coverage, the description supplies what structured fields cannot: accepted identifier families (JURITEXT, CETATEXT, CELEX, ECLI, JORFTEXT, doctrine cada:/ddd:, KALIARTI) and ambiguity handling. Return-value shapes are correctly left to the output schema, so nothing essential 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%, so the baseline is 3 and the schema does the heavy lifting; the 'Args:' block largely restates those same descriptions verbatim. The added value is the concrete call examples covering RG numbers, pourvoi ('24-14.641'), commercial court ('2024L02643'), ECHR ('6538/74') and CJEU ('C-72/24') formats, which clarify accepted syntax in a way the schema does not.

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?

Opens with a specific verb+resource+scope: 'Full text of a decision, by id or by numero (+ court).' This clearly distinguishes it from the sibling search tools (search, search_case_law, search_decisions_citing), which return lists rather than a single full document. An agent can identify the resource and the two lookup keys without opening the schema.

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?

Gives concrete selection guidance among lookup keys and the conditions under which they apply, including edge cases: a bare administrative number ('2200433') is refused, CE ambiguous numbers route through `homonymes`, and duplicate numbers return a `decisions` list. It does not explicitly name a sibling alternative (e.g., when to prefer search_case_law instead), so the when-not-to-use-this-tool dimension is left implicit.

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