Skip to main content
Glama

fiscal_ifi

Read-onlyIdempotent

Impôt sur la fortune immobilière (IFI) — IFI dû à partir du patrimoine immobilier taxable : limitation des dettes (art. 974, patrimoine > 5 M€), barème progressif (art. 977, seuil d'assujettissement 1,3 M€ mais barème dès 800 k€), décote (base 1,3–1,4 M€). Le plafonnement art. 979 (IFI + IR + PS ≤ 75 % des revenus) est appliqué SEULEMENT si revenu_foyer et autres_impots_annuels sont fournis — sinon l'IFI est rendu avant plafonnement et plafonnement_979 vaut "non_calcule" (montant non définitif). Version stateless : la base et les dettes sont des entrées (aucune lecture de dossier). (sources: CGI art. 964 (seuil 1,3 M€) ; CGI art. 977 (barème + décote) ; CGI art. 974 (limitation des dettes) ; CGI art. 979 (plafonnement 75 %))

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": {
      "patrimoine_immobilier_taxable": "<patrimoine_immobilier_taxable>"
    },
    "name": "fiscal_ifi"
  }
}

Input Schema

NameRequiredDescriptionDefault
dettesNoDettes déductibles rattachées à l'immobilier taxable (€). La limitation art. 974 s'applique au-delà de 5 M€ de patrimoine.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
revenu_foyerNoRevenus du foyer de l'année (€). Fourni → déclenche le plafonnement art. 979. Absent → IFI rendu avant plafonnement.
residence_principaleNoValeur VÉNALE de la résidence principale (€), à ne PAS inclure dans patrimoine_immobilier_taxable : l'abattement de 30 % (art. 973 I CGI) est appliqué par le calcul.
autres_impots_annuelsNoIR + prélèvements sociaux + CEHR déjà dus au titre de l'année (€), pour le calcul du plafonnement art. 979. Ignoré si revenu_foyer absent.
dette_residence_principaleNoDette restant due afférente à la résidence principale (€), à ne PAS inclure dans dettes : déductible en totalité dans la limite de la valeur imposable de la résidence (70 % de sa valeur vénale) — BOI-PAT-IFI-20-40-10 § 160.
patrimoine_immobilier_taxableYesValeur du patrimoine immobilier taxable BRUT (avant dettes) entrant dans l'assiette IFI (€) — résidence principale après abattement 30 %, biens locatifs, SCPI part immobilière, etc.

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
    • addedInput schema / properties / dette_residence_principale
      Added value: +{
      +  "default": 0,
      +  "description": "Dette restant due afférente à la résidence principale (€), à ne PAS inclure dans dettes : déductible en totalité dans la limite de la valeur imposable de la résidence (70 % de sa valeur vénale) — BOI-PAT-IFI-20-40-10 § 160.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  3. Changed1 schema field changed
    • addedInput schema / properties / residence_principale
      Added value: +{
      +  "default": 0,
      +  "description": "Valeur VÉNALE de la résidence principale (€), à ne PAS inclure dans patrimoine_immobilier_taxable : l'abattement de 30 % (art. 973 I CGI) est appliqué par le calcul.",
      +  "minimum": 0,
      +  "type": "number"
      +}
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint/idempotentHint, and the description adds genuinely useful behavior: the result may be non-definitive when plafonnement is skipped, with plafonnement_979 set to "non_calcule", and no stored dossier is consulted. Missing is any statement about output shape beyond that one field, but the conditional-result semantics are the key risk and they are disclosed.

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?

Purpose and the critical conditional branch are front-loaded in a single dense paragraph. The trailing '(sources: CGI art. ...)' list largely repeats the articles (964, 974, 977, 979) already cited inline, which is mild redundancy.

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 7-parameter calculator with no output schema, the description covers methodology, legal basis, the conditional plafonnement, and the stateless contract. It does not describe the full returned payload (only the plafonnement_979 field) or the teaser preview path beyond what the schema already says.

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 coverage is 100%, so each of the 7 parameters is already documented, including the interaction between revenu_foyer and autres_impots_annuels. The description restates that interaction and the art. 974 debt limitation threshold rather than adding new semantics, so the baseline of 3 is appropriate.

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 names a concrete computed quantity (l'impôt sur la fortune immobilière dû) and specifies the inputs feeding the computation (patrimoine brut, dettes, barème, décote, plafonnement). Even among many fiscal_* siblings, no agent could confuse this with fiscal_impot_revenu or fiscal_plus_value_immobiliere.

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 states the condition that activates the optional plafonnement branch (revenu_foyer and autres_impots_annuels must be supplied), and clarifies the stateless mode (base and dettes are inputs, no dossier is read). It does not name alternative tools, but the sibling set is tax-domain-differentiated and no ambiguity is left for this tool.

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.