Skip to main content
Glama

retraite_progressive

Read-onlyIdempotent

Retraite progressive (fraction de pension + temps partiel) — Fraction de pension perçue en travaillant à temps partiel en fin de carrière (art. L161-22-1-5). Depuis le 01/09/2025, accessible dès 60 ans (décret 2025-681) avec 150 trimestres. Fraction = 100 % − quotité travaillée (salarié 40-80 %, fonction publique 50-90 %, TNS : baisse de revenus 20-60 %). Continue d'acquérir des droits. (sources: CSS art. L161-22-1-5, D161-2-24 (décret 2025-681), R161-19-5, R161-19-6, D161-2-24-3, D161-2-24-1 ; CPCMR L89 bis, D37-1, D37-2 ; Service-Public F12842)

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": {
      "age": "<age>",
      "trimestres": "<trimestres>",
      "quotite_travail": "<quotite_travail>"
    },
    "name": "retraite_progressive"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesÂge actuel (≥ 60 depuis le 01/09/2025).
rfrNo
partsNo
statutNoStatut (insensible à la casse/accents). Reconnus : "salarié" (défaut), "fonctionnaire", "profession libérale" / "TNS" / "indépendant". Détermine la plage de quotité.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
date_effetNoDate d'effet de la retraite progressive (YYYY-MM-DD).
trimestresYesTrimestres acquis (≥ 150 requis).
date_naissanceNoYYYY-MM-DD — recale l'âge min pour une date d'effet < 01/09/2025.
quotite_travailYesQuotité de temps partiel (0-1). Salarié 0,40-0,80 ; FP 0,50-0,90.
diminution_revenusNoTNS uniquement : baisse de revenus (0,20-0,60) — alternative à quotite_travail.
pension_brute_annuelleNoPension totale brute annuelle (base + comp.) — chiffre la fraction en €.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / teaser
      Added value: +{
      +  "default": false,
      +  "description": "Aperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, closed-world), so the bar is lower. The description adds useful temporal context (rules changed on 01/09/2025, minimum age recalculated by date_naissance), but it never mentions that the tool is paywalled beyond the teaser preview — a significant behavioral trait documented only in the schema.

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 concept and formula are front-loaded effectively, but the trailing list of legal article citations (CSS, CPCMR, Service-Public) is bulky and of little operational use to an agent. The single dense paragraph also mixes conceptual definition with eligibility rules without structural separation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter calculation tool with no output schema, the description never indicates what is returned (a fraction, a euro amount via pension_brute_annuelle, an eligibility verdict). It explains the domain well but leaves the agent guessing about the result shape and the teaser/payment mechanic.

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?

With 82% schema description coverage, the baseline is 3. The description reinforces the statut-dependent quotité ranges (40–80% salarié, 50–90% fonction publique, 20–60% TNS) and the 100% − quotité formula, but this largely restates what the schema already says per parameter.

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 clearly establishes the resource: the progressive-retirement fraction (pension fraction combined with part-time work), including the governing formula and legal basis. It stops short of an explicit action verb (e.g., 'computes' or 'simulates') and never names a sibling, so differentiation comes from the subject matter rather than the wording.

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?

Eligibility conditions are spelled out (accessible from age 60 since 01/09/2025 with 150 trimestres), which implicitly tells the agent when this regime applies. However, there is no explicit when-to-use/when-not guidance and no routing against siblings like retraite_estimation or retraite_rachat.

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.