Skip to main content
Glama

fiscal_cdhr

Read-onlyIdempotent

Contribution différentielle sur les hauts revenus (CDHR) — CDHR due (art. 224 CGI) : imposition minimale de 20 % du RFR ajusté − imposition effective (IR au barème + PFU 12,8 % sur les revenus financiers + CEHR + majorations 12 500 €/couple et 1 500 €/personne à charge), après décote art. 224 V. DISTINCTE de la CEHR (art. 223 sexies). Version stateless. Montant ADDITIONNEL, dû en plus de l'IR (fiscal_impot_revenu) et de la CEHR (fiscal_cehr), déjà déduits dans son calcul : l'additionner, ne pas le substituer. (sources: CGI art. 224 (CDHR) ; CGI art. 223 sexies (CEHR) ; FAQ CDHR impots.gouv.fr)

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": {
      "revenu_fiscal_reference": "<revenu_fiscal_reference>"
    },
    "name": "fiscal_cdhr"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsNoParts de quotient familial.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
situationNoSituation familiale (seuils célib 250 k / couple 500 k, majoration 12 500 € couple).Célibataire
rfr_ajusteNoRFR ajusté art. 224 II (assiette CDHR) si connu. Absent → = RFR.
parent_isoleNoParent isolé (case T, art. 194 II CGI) : célibataire ou divorcé vivant seul avec au moins un enfant à charge. La part du 1er enfant est alors plafonnée à 4 262 € (art. 197 I-2) au lieu de 2 × 1 807 €. Les parts transmises doivent déjà inclure la demi-part case T.
impot_referenceNoImposition effective exacte de la déclaration (€). Absent → reconstruite (IR barème + PFU + CEHR + majorations).
demi_parts_195_abeNoDemi-parts de l'art. 195-1 a, b ou e CGI (personne vivant seule ayant élevé seule un enfant 5 ans, enfant décédé, enfant adopté) incluses dans les parts : plafonnées à 1 079 € chacune.
residence_alterneeNoAvec parent_isole : enfants UNIQUEMENT en résidence alternée — la demi-part de chacun des deux premiers enfants est plafonnée à 2 131 € (art. 197 I-2 CGI). Les parts transmises doivent inclure les majorations de 0,25 (art. 194 I).
nb_personnes_chargeNoPersonnes à charge (majoration 1 500 € chacune de l'imposition de référence).
demi_parts_invaliditeNoDemi-parts d'invalidité ou d'ancien combattant (art. 195-1 c, d, d bis, f et 195-2 à 6 CGI) incluses dans les parts : plafond de droit commun + réduction de 1 801 € chacune quand le plafonnement joue.
revenus_financiers_pfuNoRevenus financiers imposés au PFU 12,8 % (dividendes + intérêts) inclus dans le RFR (€) — corrige l'imposition de référence.
revenu_fiscal_referenceYesRFR du foyer (€).

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. Changed4 schema fields changed
    • addedInput schema / properties / demi_parts_195_abe
      Added value: +{
      +  "default": 0,
      +  "description": "Demi-parts de l'art. 195-1 a, b ou e CGI (personne vivant seule ayant élevé seule un enfant 5 ans, enfant décédé, enfant adopté) incluses dans les parts : plafonnées à 1 079 € chacune.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / demi_parts_invalidite
      Added value: +{
      +  "default": 0,
      +  "description": "Demi-parts d'invalidité ou d'ancien combattant (art. 195-1 c, d, d bis, f et 195-2 à 6 CGI) incluses dans les parts : plafond de droit commun + réduction de 1 801 € chacune quand le plafonnement joue.",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / parent_isole
      Added value: +{
      +  "default": false,
      +  "description": "Parent isolé (case T, art. 194 II CGI) : célibataire ou divorcé vivant seul avec au moins un enfant à charge. La part du 1er enfant est alors plafonnée à 4 262 € (art. 197 I-2) au lieu de 2 × 1 807 €. Les parts transmises doivent déjà inclure la demi-part case T.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / residence_alternee
      Added value: +{
      +  "default": false,
      +  "description": "Avec parent_isole : enfants UNIQUEMENT en résidence alternée — la demi-part de chacun des deux premiers enfants est plafonnée à 2 131 € (art. 197 I-2 CGI). Les parts transmises doivent inclure les majorations de 0,25 (art. 194 I).",
      +  "type": "boolean"
      +}
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds genuinely non-obvious behavior: statelessness, the additive-vs-substitutive semantic, and the exact composition of the reference imposition (barème IR + PFU 12.8% + CEHR + 12 500 €/couple and 1 500 €/person allowances) plus the art. 224 V décote. It does not describe output shape or what happens at the threshold boundary, but the mutation-risk questions an agent would have are answered, with no contradiction of the annotations.

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 core identity is front-loaded in the first clause, and every element (formula, sibling exclusion, additive rule) carries information. However, it is delivered as a single run-on sentence with inline arithmetic and parenthetical article citations, followed by a fragment, which makes it slow to parse for an agent scanning for the operative rule.

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 12-parameter tax computation with no output schema, the description supplies the formula, the base, the interaction with sibling tools, and the stateless contract — enough for an agent to know when and how to call it and how to combine the result. The remaining gap (exact returned field names) is partially anticipated by the teaser parameter's mention of a headline figure with confidence and sources.

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 adds real meaning: it explains what the 'imposition effective' actually comprises (barème + PFU 12.8% + CEHR + majorations), which is exactly what the impot_reference parameter rebuilds when absent. It also frames revenu_fiscal_reference/rfr_ajuste as the assiette (art. 224 II). The remaining 10 parameters gain nothing from the prose beyond the schema.

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 states precisely what is computed: the CDHR under art. 224 CGI, defined as a 20% minimum levy on adjusted RFR minus effective taxation, and explicitly marks it 'DISTINCTE de la CEHR (art. 223 sexies)'. It names the two sibling results it stacks on (fiscal_impot_revenu, fiscal_cehr), so an agent can separate it from them. It never uses an explicit verb like 'calcule/renvoie', leaving the compute-and-return framing implicit.

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?

Gives a concrete aggregation rule: the amount is ADDITIONAL and must be added to IR and CEHR, not substituted for them ('l'additionner, ne pas le substituer'). It also tells the agent this is stateless, implying independent per-call computation. It stops short of stating when the tool is irrelevant (e.g., RFR below the 250k/500k triggers, where CDHR would be zero) — those thresholds appear only in the situation parameter description.

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.