Skip to main content
Glama

justicelibre

by io.github.Dahliyaal
OverviewDiscussionsAdmin

search_recent_admin_decisions

Read-onlyIdempotent

Latest decisions from the administrative courts' open data (daily mirror), sorted by date: what a court has just decided (by relevance: search_case_law).

All words required (singular or plural); "in double quotes": exact form; OR/AND/NOT/NEAR in UPPERCASE between two words are operators (NEAR = within 10 words); lowercase words are plain words. Keywords in French: judgments spell out the full expression, rarely the acronym ("OQTF").

Example: search_recent_admin_decisions(query='"obligation de quitter le territoire"', court="TA59")

Args: query: keywords; empty = all decisions of the court court: CE | CE-CAA (CE + CAA) | code of a TA or CAA ("TA59", "CAA69") | ALL_TA (the 40 TA) | ALL_CAA (the 9 CAA) limit: results (one court; max 100) limit_per_court: results per court (ALL_TA, ALL_CAA; max 100) total_limit: overall cap (ALL_TA, ALL_CAA; 0 = no cap) date_min, date_max: YYYY-MM-DD, date of the decision (optional)

Input Schema

NameRequiredDescriptionDefault
courtNoCE | CE-CAA (CE + CAA) | code of a TA or CAA ("TA59", "CAA69") | ALL_TA (the 40 TA) | ALL_CAA (the 9 CAA)CE
limitNoresults (one court; max 100)
queryNokeywords; empty = all decisions of the court
date_maxNoDate de fin incluse, format AAAA-MM-JJ (ex. « 2024-12-31 »). Vide = pas de borne.
date_minNoDate de début incluse, format AAAA-MM-JJ (ex. « 2020-01-01 »). Vide = pas de borne.
total_limitNooverall cap (ALL_TA, ALL_CAA; 0 = no cap) date_min, date_max: YYYY-MM-DD, date of the decision (optional)
limit_per_courtNoresults per court (ALL_TA, ALL_CAA; max 100)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / date_max
      Added value: +{
+  "default": "",
+  "description": "Date de fin incluse, format AAAA-MM-JJ (ex. « 2024-12-31 »). Vide = pas de borne.",
+  "title": "Date Max",
+  "type": "string"
+}
    • addedInput schema / properties / date_min
      Added value: +{
+  "default": "",
+  "description": "Date de début incluse, format AAAA-MM-JJ (ex. « 2020-01-01 »). Vide = pas de borne.",
+  "title": "Date Min",
+  "type": "string"
+}
    • changedInput schema / properties / total_limit / description
      Previous value: -"overall cap (ALL_TA, ALL_CAA; 0 = no cap)"New value: +"overall cap (ALL_TA, ALL_CAA; 0 = no cap) date_min, date_max: YYYY-MM-DD, date of the decision (optional)"
  2. Changed5 schema fields changed
    • changedInput schema / properties / court / description
      Previous value: -"CE | CE-CAA (CE + CAA) | code d'un TA ou d'une CAA (« TA59 », « CAA69 ») | ALL_TA (les 40 TA) | ALL_CAA (les 9 CAA)"New value: +"CE | CE-CAA (CE + CAA) | code of a TA or CAA (\"TA59\", \"CAA69\") | ALL_TA (the 40 TA) | ALL_CAA (the 9 CAA)"
    • changedInput schema / properties / limit / description
      Previous value: -"résultats (une juridiction)"New value: +"results (one court; max 100)"
    • changedInput schema / properties / limit_per_court / description
      Previous value: -"résultats par juridiction (ALL_TA, ALL_CAA)"New value: +"results per court (ALL_TA, ALL_CAA; max 100)"
    • changedInput schema / properties / query / description
      Previous value: -"mots-clés ; vide = toutes les décisions de la juridiction"New value: +"keywords; empty = all decisions of the court"
    • changedInput schema / properties / total_limit / description
      Previous value: -"plafond global (ALL_TA, ALL_CAA ; 0 = pas de plafond)"New value: +"overall cap (ALL_TA, ALL_CAA; 0 = no cap)"
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: it is a daily mirror of open data, dates refer to the decision date, and per-call caps are bounded (max 100, 0 = no cap), which matters for pagination expectations.

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 purpose and query-syntax rules are front-loaded well, but the trailing 'Args:' block largely restates the input schema verbatim, adding length without new meaning. The structure is legible yet carries redundancy an agent does not need twice.

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 7 optional parameters, full schema coverage, rich annotations, and an output schema that already documents return values, the description supplies everything still missing: the query language, the court-mode semantics, and the cap behavior. Nothing an agent needs to invoke it correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it by documenting query syntax that the schema does not: all words required, double quotes for exact phrases, uppercase OR/AND/NOT/NEAR operators, and the French-keyword caveat about acronyms such as 'OQTF'. That is real semantic value for the highest-risk parameter.

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 and scope: 'Latest decisions from the administrative courts' open data (daily mirror), sorted by date'. It also explicitly differentiates itself from the closest sibling by naming the recency-vs-relevance distinction against `search_case_law`, so an agent can pick between them without opening either 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?

The parenthetical '(by relevance: `search_case_law`)' routes the agent to the alternative and implies the selection rule (this tool for latest-by-date, the sibling for relevance search). However, there are no explicit when-not conditions and no guidance on the combinatorial court modes (ALL_TA vs ALL_CAA vs CE-CAA) beyond the enum listing.

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