justicelibre

search_case_law

Read-onlyIdempotent

Decisions of one court or court family, by relevance or by date (latest decisions: search_recent_admin_decisions). Keywords in French. ECHR, CJEU: texts sometimes in English only.

Example: search_case_law(query="licenciement inaptitude", court="CASS")

Input Schema

Name	Required	Description	Default
`sort`	No	relevance \| date_desc \| date_asc (ADMIN, CE, CAA, TA, CNDA)	relevance
`court`	No	ADMIN (CE+CAA+TA, default) \| CE \| CAA \| TA \| ARIANEWEB \| JUDICIAIRE \| CASS \| CA \| TJ \| TCOM \| CONSTIT \| CEDH \| CJUE \| CNDA
`limit`	No	per page (max 50)
`query`	No	keywords (optional with numero_rg), plural included except "in double quotes"; OR/AND/NOT/NEAR in UPPERCASE between two words are operators (NEAR = within 10 words); lowercase words are plain words
`nature`	No	QPC, DC… (CONSTIT)
`offset`	No	pagination (pass next_offset as is)
`date_max`	No	same
`date_min`	No	YYYY-MM-DD (not ARIANEWEB, CEDH, CJUE)
`numero_rg`	No	RG number (CA, JUDICIAIRE)
`court_name`	No	"TA Lille", "CAA Douai" (ADMIN, CE, CAA, TA)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

changedInput schema / properties / court / default
```
Previous value: -"ADMIN"New value: +""
```

changedInput schema / properties / court / description

Previous value: -"ADMIN (CE+CAA+TA) | CE | CAA | TA | ARIANEWEB | JUDICIAIRE | CASS | CA | TJ | TCOM | CONSTIT | CEDH | CJUE | CNDA"New value: +"ADMIN (CE+CAA+TA, default) | CE | CAA | TA | ARIANEWEB | JUDICIAIRE | CASS | CA | TJ | TCOM | CONSTIT | CEDH | CJUE | CNDA"

Changed3 schema fields changedOct 19, 2026

changedInput schema / properties / court / description

Previous value: -"ADMIN (CE+CAA+TA) | CE | CAA | TA | ARIANEWEB | JUDICIAIRE | CASS | CA | TJ | TCOM | CONSTIT | CEDH | CJUE"New value: +"ADMIN (CE+CAA+TA) | CE | CAA | TA | ARIANEWEB | JUDICIAIRE | CASS | CA | TJ | TCOM | CONSTIT | CEDH | CJUE | CNDA"

changedInput schema / properties / limit / description

Previous value: -"results per page (max 50)"New value: +"per page (max 50)"

changedInput schema / properties / sort / description

Previous value: -"relevance | date_desc | date_asc (ADMIN, CE, CAA, TA)"New value: +"relevance | date_desc | date_asc (ADMIN, CE, CAA, TA, CNDA)"

Changed7 schema fields changedOct 15, 2026

changedInput schema / properties / court_name / description

Previous value: -"« TA Lille », « CAA Douai » (ADMIN, CE, CAA, TA)"New value: +"\"TA Lille\", \"CAA Douai\" (ADMIN, CE, CAA, TA)"

changedInput schema / properties / date_max / description
```
Previous value: -"idem"New value: +"same"
```

changedInput schema / properties / date_min / description

Previous value: -"AAAA-MM-JJ (pas ARIANEWEB, CEDH, CJUE)"New value: +"YYYY-MM-DD (not ARIANEWEB, CEDH, CJUE)"

changedInput schema / properties / limit / description

Previous value: -"résultats par page"New value: +"results per page (max 50)"

changedInput schema / properties / numero_rg / description

Previous value: -"n° RG de cour d'appel (CA, JUDICIAIRE)"New value: +"RG number (CA, JUDICIAIRE)"

changedInput schema / properties / offset / description

Previous value: -"pagination"New value: +"pagination (pass next_offset as is)"

changedInput schema / properties / query / description

Previous value: -"mots-clés, pluriel inclus sauf \"entre guillemets\" (facultatif avec numero_rg)"New value: +"keywords (optional with numero_rg), plural included except \"in double quotes\"; OR/AND/NOT/NEAR in UPPERCASE between two words are operators (NEAR = within 10 words); lowercase words are plain words"

Changed2 schema fields changedOct 11, 2026

changedInput schema / properties / query / description

Previous value: -"mots-clés (facultatif avec numero_rg)"New value: +"mots-clés, pluriel inclus sauf \"entre guillemets\" (facultatif avec numero_rg)"

removedInput schema / properties / session_token

Removed value: -{
-  "default": "",
-  "description": "jeton PISTE : Judilibre en direct (judiciaire)",
-  "title": "Session Token",
-  "type": "string"
-}

AddedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful operational constraints beyond annotations, such as French keywords, English-only ECHR/CJEU texts, and court-specific limits on date filtering and sorting.

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 front-loaded with purpose and the key sibling alternative, then presents concise parameter notes. Some entries repeat the schema or are terse to the point of being unclear (`date_max: same`), but there is little wasted text.

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?

With 10 optional parameters, an output schema, and rich annotations, the description provides enough context to call the tool correctly: court options, sorting, date constraints, pagination behavior, query syntax, and known language limitations.

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 parameter meanings are already documented. The description largely repeats schema text, though it adds a concrete example and clarifies that `query` is optional when `numero_rg` is provided.

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: retrieving decisions of one court or court family by relevance or date. It explicitly distinguishes the latest-administrative-decisions use case by naming the sibling tool `search_recent_admin_decisions`.

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 clear context for when to use this tool, including an example query and court codes, and routes 'latest decisions' to `search_recent_admin_decisions`. It lacks explicit when-not-to-use guidance beyond that one alternative.

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

All justicelibre tools Inspect

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.