Skip to main content
Glama

Lexou · droit français

Plafonds de l'aide juridictionnelle 2026

plafonds_aide_juridictionnelle
Read-onlyIdempotent

Plafonds 2026 de l'aide juridictionnelle (circulaire du 16 janvier 2026, fiche Service-Public F18074) selon le nombre de personnes du foyer fiscal : revenu fiscal de référence pour l'aide totale, à 55 % et à 25 %, patrimoine mobilier et immobilier hors résidence principale. Avec le revenu fiscal de référence, rend aussi la tranche probable. Pas pour l'aide juridictionnelle d'un autre pays de l'Union.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "personnes": "<personnes>"
    },
    "name": "plafonds_aide_juridictionnelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
personnesYesNombre de personnes du foyer fiscal (une même déclaration de revenus)
patrimoine_mobilierNoÉpargne et placements, en euros
protection_juridiqueNoUne assurance de protection juridique couvre-t-elle déjà le litige ?
revenu_fiscal_referenceNoRevenu fiscal de référence du dernier avis d'imposition, en euros
patrimoine_immobilier_hors_residenceNoBiens immobiliers hors résidence principale, en euros

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A3.7/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 needs no restating. The description adds real value beyond them: the legal sources and their date, the three thresholds computed, that patrimoine immobilier is counted hors résidence principale, and that a probable tranche is returned when RFR is supplied. It does not explain how the protection_juridique input changes the answer.

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 core resource and its three threshold levels are front-loaded in the opening clause, followed by two short sentences covering the derived output and the geographic exclusion. Information density is high with no filler, though the first sentence is long and packs source citations that an invoking agent may not need.

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?

With five parameters, no output schema, and a deterministic lookup, the description does the necessary work: it enumerates the values returned (thresholds at 100/55/25 percent, asset ceilings, probable tranche), so an agent knows what comes back. The remaining gap is the unexplained effect of protection_juridique on the result.

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 all five parameters are already documented and the baseline is 3. The description reinforces the meaning of patrimoine hors résidence principale and the RFR-to-tranche relationship, but it says nothing about the protection_juridique boolean, which is the parameter whose effect is least obvious from the schema alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the exact resource (plafonds 2026 de l'aide juridictionnelle), its authoritative sources (circulaire du 16 janvier 2026, fiche Service-Public F18074), and the three threshold levels it returns. An agent can tell this is a French legal-aid ceiling lookup keyed on household size. It stops short of a 5 because it never contrasts itself with a potentially overlapping sibling such as fiche_service_public, which it cites as a source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers it should call this when it needs legal-aid income ceilings for a French household. One explicit exclusion is given ("Pas pour l'aide juridictionnelle d'un autre pays de l'Union"), but no positive when-to-use condition and no named alternative tool are offered.

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