Skip to main content
Glama

retraite_ps_pension

Read-onlyIdempotent

Prélèvements sociaux sur une pension (brut → net) — CSG (taux 0/3,8/6,6/8,3 % selon le RFR et les parts) + CRDS + CASA + 1 % maladie sur la part de pension complémentaire. Rend la pension nette, la tranche CSG et le taux effectif. Barème 2026 (seuils RFR 2024). Pensions de retraite uniquement ; pour un revenu du capital → fiscal_prelevements_sociaux. (sources: CSS art. L136-8 (CSG pensions) ; CSS art. L131-2 (1 % maladie retraite complémentaire) ; Barème CSG des pensions 2026 (seuils RFR 2024, circulaire CNAV 22/12/2025))

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": {
      "pension_annuelle_brute": "<pension_annuelle_brute>"
    },
    "name": "retraite_ps_pension"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfrNoRevenu fiscal de référence 2024 du foyer (€) — détermine la tranche CSG. Si absent, la pension sert de proxy et la tranche est « estimée ».
partsNoParts fiscales du foyer (interpolation linéaire des seuils entre 1 et 2 parts).
rfr_n3NoOptionnel : RFR 2023 (avis 2024). Lissage CSS L.136-8 III 2° : s'il est ≤ au seuil du taux réduit 2025 (16 755 € + 4 474 € par demi-part), le taux de 3,8 % est maintenu.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
parts_n3NoOptionnel : parts fiscales de l'avis 2024 (défaut = parts).
montant_complementaireNoPart de la pension soumise au 1 % maladie (tranches médiane/normale) : complémentaires de SALARIÉS (Agirc-Arrco, Ircantec, CRPN). Les pensions d'activité indépendante (libéraux, RCI…) en sont exclues (CSS L.131-2 1°). Défaut 0.
pension_annuelle_bruteYesPension annuelle brute totale (€).

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. Changed1 schema field changed
    • changedInput schema / properties / montant_complementaire / description
      Previous value: -"Part de la pension relevant d'un régime complémentaire (Agirc-Arrco, Ircantec, CRPN, comp. libéraux…), soumise en plus au 1 % maladie aux tranches médiane/normale. Défaut 0 = base seule."New value: +"Part de la pension soumise au 1 % maladie (tranches médiane/normale) : complémentaires de SALARIÉS (Agirc-Arrco, Ircantec, CRPN). Les pensions d'activité indépendante (libéraux, RCI…) en sont exclues (CSS L.131-2 1°). Défaut 0."
  3. Changed2 schema fields changed
    • addedInput schema / properties / parts_n3
      Added value: +{
      +  "description": "Optionnel : parts fiscales de l'avis 2024 (défaut = parts).",
      +  "minimum": 1,
      +  "type": "number"
      +}
    • addedInput schema / properties / rfr_n3
      Added value: +{
      +  "description": "Optionnel : RFR 2023 (avis 2024). Lissage CSS L.136-8 III 2° : s'il est ≤ au seuil du taux réduit 2025 (16 755 € + 4 474 € par demi-part), le taux de 3,8 % est maintenu.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  4. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint=false, and the description adds the legal basis, the applicable 2026 barème with 2024 RFR thresholds, and the exact return values. It does not mention the paid/free-preview gating or any limitation of the estimate beyond what the schema's 'teaser' parameter conveys, leaving a small gap.

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?

Front-loaded with purpose, then scope, then exclusions, then sources — a sensible order. The trailing legal-citation parenthetical is long, though defensible for a tax-calculation tool; the tier enumeration is dense but informative.

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?

For a 7-parameter calculation tool with no output schema, the description states the return values (net pension, CSG tranche, effective rate), the applicable regime year, and the domain boundary. Nothing an agent needs in order to call it correctly is missing.

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 every parameter is already documented, including rfr proxy behavior and the eligible complementary-pension scope. The description repeats the high-level logic of the CSG tiers but adds no syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific computation (gross pension → net after social levies) with named components (CSG, CRDS, CASA, 1% maladie) and the output values it produces. It also explicitly separates itself from fiscal_prelevements_sociaux for capital income, so an agent can route correctly without opening a schema.

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?

Explicit scope sentence: 'Pensions de retraite uniquement' plus a named alternative ('pour un revenu du capital → fiscal_prelevements_sociaux'). The schema-documented proxy behavior when RFR is absent further defines when the tool still applies.

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.