Skip to main content
Glama

justicelibre

by io.github.Dahliyaal
OverviewDiscussionsAdmin

search_admin

Read-only

Recherche pondérée par pertinence BM25 sur la jurisprudence administrative complète (Conseil d'État + Tribunal des conflits + 9 CAA + 40 TA — pour le TC, filtrer avec juridiction="conflits").

Source : bulk JADE DILA (~550 k décisions full text). Contrairement aux
outils `search_admin_recent*` qui trient par date, celui-ci classe par
pertinence sémantique des mots-clés. Indispensable pour trouver LES
bonnes décisions sur un sujet sans dépendre de l'ancienneté.

⚠️ **Si tu cherches par numéro de requête (7 chiffres ex: 2200433)**,
utilise plutôt `get_admin_decision(numero, juridiction=...)` qui fait
un lookup SQL exact. La recherche FTS5 d'un numéro court ne le trouve
que dans les décisions qui le **citent** dans leur texte (ex: décision
de cassation), pas la décision identifiée par ce numéro.

Args:
    query: mots-clés (opérateurs FTS5 : AND/OR/NOT, "phrase exacte", mot*)
    juridiction: filtre d'ORIGINE (depuis le 8 septembre 2026). Accepte
        un code (`CE`, `CAA59`, `TA69`, `TC`), un nom complet (« Tribunal
        administratif de Lille ») ou une forme courte (« TA Lille »,
        « CAA Douai »). La base écrit la même cour de plusieurs façons
        (« CAA de LYON », « Cour administrative d'appel de Lyon »…) : le
        filtre les couvre toutes, et ne renvoie QUE des décisions rendues
        par cette juridiction. La réponse porte `juridiction_filtre`
        quand le filtre est actif. ⚠️ Valeur NON reconnue (une ville nue
        « Lyon », une faute de frappe) : elle est alors ajoutée comme
        mot-clé à la requête — les décisions qui la CITENT remontent
        aussi — et la réponse le dit dans `note`. Codes : `list_juridictions`.
    sort: "relevance" (défaut, BM25) ou "date_desc" / "date_asc"
    date_min: limite inférieure ISO YYYY-MM-DD (optionnel)
    date_max: limite supérieure ISO YYYY-MM-DD (optionnel)
    limit: nombre de résultats (défaut 20, max 50)
    offset: pagination

Returns:
    {"total", "returned", "decisions": [...]} avec extracts BM25.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNorelevance
limitNo
queryYes
offsetNo
date_maxNo
date_minNo
juridictionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A5/5.0
Behavior5/5

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

With readOnlyHint=true, the annotation already signals safety, and the description adds substantial behavioral context: BM25 ranking, full-text corpus size, FTS5 operator support, jurisdiction filter aliasing, and the documented fallback behavior for unrecognized jurisdiction values where the value becomes a keyword and the response notes it.

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?

Although long, every section earns its place: purpose, sibling differentiation, a high-value routing warning, and a structured Args block. The most important operational caveats are front-loaded, and the format follows the schema's parameter order.

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 7 parameters, zero schema description coverage, and a non-trivial jurisdiction filtering quirk, the description is complete. It covers ranking behavior, filters, pagination, result shape, sibling alternatives, and malformed input handling, leaving no critical gap for an agent to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it fully compensates. Every parameter is explained with types, defaults, accepted values, and practical examples, including a detailed warning about `juridiction` normalization and the `note` field behavior.

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: 'Recherche pondérée par pertinence BM25 sur la jurisprudence administrative complète', enumerating the exact courts covered. It also distinguishes itself from `search_admin_recent*` by explaining the relevance-based ordering, making it easy to select among 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?

The description explicitly contrasts with `search_admin_recent*` tools and tells the agent this tool is for finding the best decisions on a topic regardless of age. It also gives a clear exclusion: for 7-digit request numbers, use `get_admin_decision` instead, because FTS5 only finds citations, not the ruling itself.

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

All justicelibre toolsInspect
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.

Resources