Skip to main content
Glama

fiscal_cehr

Read-onlyIdempotent

Contribution exceptionnelle sur les hauts revenus (CEHR) — CEHR due sur le revenu fiscal de référence (art. 223 sexies CGI). Distincte de la CDHR. S'ajoute à l'IR au barème (fiscal_impot_revenu) ; la CDHR (fiscal_cdhr) peut s'y ajouter en complément. (sources: CGI art. 223 sexies ; BOFiP BOI-IR-CHR)

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_cehr"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfr_n1NoOptionnel : RFR de l'année précédente. Avec rfr_n2, active le lissage des revenus exceptionnels (art. 223 sexies II-1).
rfr_n2NoOptionnel : RFR de l'avant-dernière année (lissage, avec rfr_n1).
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élibataire 250 k / couple 500 k).Célibataire
revenu_fiscal_referenceYesRevenu fiscal de référence 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. Changed2 schema fields changed
    • addedInput schema / properties / rfr_n1
      Added value: +{
      +  "description": "Optionnel : RFR de l'année précédente. Avec rfr_n2, active le lissage des revenus exceptionnels (art. 223 sexies II-1).",
      +  "minimum": 0,
      +  "type": "number"
      +}
    • addedInput schema / properties / rfr_n2
      Added value: +{
      +  "description": "Optionnel : RFR de l'avant-dernière année (lissage, avec rfr_n1).",
      +  "minimum": 0,
      +  "type": "number"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false, idempotentHint=true), so the description's added value is in disclosing that the result is additive rather than a standalone total. LEGAL sources are cited, reinforcing traceability, but the description says nothing about the response shape or what the teaser preview actually returns.

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?

Three short, front-loaded sentences with the identification first, the sibling distinction second, and the compositional relationship last, followed by source citations. It is dense but telegraphic, with some information (thresholds) left to the schema.

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?

There is no output schema, so the description must carry the burden of explaining what is returned — amount, rate, smoothing applied, currency — and it does not. For a read-only single-objective calculator this is a notable gap, though the legal and dependency context partially compensates.

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%, with all five parameters — including the rfr_n1/rfr_n2 smoothing pair, the situation enum, and the teaser flag — documented in the schema itself. The description adds no parameter-level meaning beyond that, so the baseline 3 is appropriate.

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 specific tax (CEHR), states it is computed on the RFR, and cites the legal basis (CGI art. 223 sexies). It explicitly distinguishes itself from the sibling tools fiscal_cdhr and fiscal_impot_revenu, though the computational verb is only implied rather than stated.

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 gives clear context on how the CEHR composes with other tools — it adds on top of the barème income tax (fiscal_impot_revenu) and the CDHR (fiscal_cdhr) may be added on top of it — which lets an agent sequence calls correctly. It stops short of stating outright when not to use this tool or what precondition (e.g. RFR above threshold) selects it.

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.