Skip to main content
Glama

tax-retirement

by io.github.herve-coulon
OverviewDiscussionsAdmin

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)

Input Schema

TableJSON 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).
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. 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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds domain context (legal article, BOFiP source, stacking behavior with IR/CDHR) but says nothing about the computed output or edge cases, and with no output schema that would have been useful.

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?

A single dense sentence with the resource and legal basis front-loaded, followed by sibling disambiguation. The parenthetical source citation is defensible for a tax tool but is the least load-bearing element.

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 read-only calculator whose annotations cover the safety profile and whose schema fully documents all four parameters, the description supplies the missing domain framing (legal basis, sibling relationships). Only the return shape is unaddressed, which is a minor gap given no output schema exists.

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%, and the schema itself documents the RFR smoothing mechanism (rfr_n1/rfr_n2) and the single/couple thresholds. The description only names the required RFR input, adding no semantics beyond what the schema already provides. 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 tax computation (CEHR) on a specific base (revenu fiscal de référence), cites its legal basis (art. 223 sexies CGI), and explicitly distinguishes it from the two siblings it is most likely to be confused with (fiscal_cdhr and fiscal_impot_revenu). An agent can route to it without opening any schema.

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 explicitly states the relationship to alternatives: it is distinct from CDHR, it is added on top of the barème IR (fiscal_impot_revenu), and CDHR (fiscal_cdhr) may stack on top of it. That is close to when-to-use guidance, though it never states a negative condition such as 'do not use for the CDHR itself' in imperative form.

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