Skip to main content
Glama

tax-retirement

by io.github.herve-coulon
OverviewDiscussionsAdmin

fiscal_flat_tax_vs_bareme

Read-onlyIdempotent

PFU (flat tax) vs barème progressif — Compare l'imposition d'un revenu du capital au PFU (12,8 % IR + PS) vs à l'option barème (case 2OP : abattement 40 % dividendes, CSG 6,8 % déductible, IR marginal), et dit quelle option est la plus favorable. Taux PS 2026 par nature (18,6 % mobilier, 17,2 % AV/immo). Version stateless. (sources: CGI art. 200 A (PFU + option 2OP) ; CGI art. 158-3-2° (abattement 40 %) ; CGI art. 154 quinquies (CSG déductible) ; LFSS 2026 art. 12 (PS par nature))

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
partsNoParts de quotient familial.
montantYesMontant du revenu / gain (€).
situationNoSituation familiale.Célibataire
av_encoursNoPour av_plus8ans : primes versées par le BÉNÉFICIAIRE des produits sur l'ensemble de ses contrats, non remboursées (€). Seuil de 150 000 € par bénéficiaire, indépendant de la situation familiale (art. 200 A 1-B-2° CGI) : au-delà, 7,5 % sur la fraction 150 000 / primes et 12,8 % sur le reste. Abattement 4 600 / 9 200 € imputé d'abord sur la part à 7,5 %.
type_revenuYesNature du revenu du capital.
av_primes_avant_2017NoPour av_plus8ans : primes versées AVANT le 27/09/2017 par ce bénéficiaire (€). Elles réduisent le seuil de 150 000 € et leurs produits passent en premier pour l'abattement (art. 125-0 A et 200 A CGI).
revenu_net_imposableYesRevenu net imposable du foyer HORS ce revenu (€) — détermine la TMI pour l'option barème.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / av_encours / description
      Previous value: -"Pour av_plus8ans : encours total des primes (détermine le taux réduit 7,5 % vs 12,8 %) (€)."New value: +"Pour av_plus8ans : primes versées par le BÉNÉFICIAIRE des produits sur l'ensemble de ses contrats, non remboursées (€). Seuil de 150 000 € par bénéficiaire, indépendant de la situation familiale (art. 200 A 1-B-2° CGI) : au-delà, 7,5 % sur la fraction 150 000 / primes et 12,8 % sur le reste. Abattement 4 600 / 9 200 € imputé d'abord sur la part à 7,5 %."
    • addedInput schema / properties / av_primes_avant_2017
      Added value: +{
+  "default": 0,
+  "description": "Pour av_plus8ans : primes versées AVANT le 27/09/2017 par ce bénéficiaire (€). Elles réduisent le seuil de 150 000 € et leurs produits passent en premier pour l'abattement (art. 125-0 A et 200 A CGI).",
+  "minimum": 0,
+  "type": "number"
+}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark it as read-only, idempotent, and closed-world. The description adds useful behavioral context beyond annotations by stating it is stateless and by specifying the calculation rules, applicable rates, and legal references.

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 description is dense but front-loads the core comparison and tax outcome before adding legal details. The parenthetical source list is long, but the complexity of the domain justifies most of the length.

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?

For a complex tax calculation tool with no output schema, the description explains what is compared, the relevant rates, and the stateless behavior. It could be more explicit about the exact return structure, but the core invocation needs are well covered by the schema and annotations.

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. The description adds meaningful context beyond the schema by explaining that PS rates depend on the nature of the income and by referencing the 2OP option, the 40% dividend allowance, and deductible CSG.

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 comparison: PFU flat tax versus barème progressif for capital income, and says it determines the more favorable option. It also specifies the tax scope and rates, making it clearly distinguishable from sibling fiscal tools such as fiscal_tmi or fiscal_prelevements_sociaux.

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?

It clearly indicates the context of use: comparing the taxation of a capital income under PFU versus the barème option. However, it does not explicitly name alternative tools or state when not to use this tool versus related fiscal simulations.

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

All tax-retirement 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