Skip to main content
Glama

fiscal_per_plafond

Read-onlyIdempotent

Plafond de déduction PER de l'année — Plafond de versement PER déductible du revenu de l'année. Salarié (art. 163 quatervicies CGI) : 10 % des revenus pro et du PASS de l'année N-1 (versements 2026 → PASS 2025 = 47 100 €, plancher 4 710 €, max 37 680 €). TNS/BNC (art. 154 bis) : 10 % du bénéfice + 15 % de la fraction entre 1 et 8 PASS de l'année N (PASS 2026 = 48 060 €, plancher 4 806 €). Version « express » : un seul revenu, HORS reliquats et HORS mutualisation entre conjoints. C'est un PLAFOND de déduction, PAS une économie d'impôt : pour le gain d'un versement → fiscal_per_gain. Ne jamais multiplier ce plafond (ou un versement) par fiscal_tmi. (sources: CGI art. 163 quatervicies (salariés) ; CGI art. 154 bis (TNS/BNC) ; PASS 2026 — arrêté 22/12/2025 (JO 23/12/2025))

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_professionnel": "<revenu_professionnel>"
    },
    "name": "fiscal_per_plafond"
  }
}

Input Schema

NameRequiredDescriptionDefault
tnsNoVrai = TNS/BNC (art. 154 bis, tranche majorée 15 % entre 1 et 8 PASS) ; faux = salarié (art. 163 quatervicies).
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
revenu_professionnelYesRevenu professionnel net (€). Salarié : salaires APRÈS la déduction forfaitaire de 10 % ou les frais réels (art. 83 3°, auquel renvoie le 163 quatervicies II 1°) — ex. 60 000 € déclarés → 54 000 €. TNS/BNC : bénéfice imposable.

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
    • changedInput schema / properties / revenu_professionnel / description
      Previous value: -"Revenu professionnel net (salaire net imposable, ou bénéfice pour un TNS/BNC) (€)."New value: +"Revenu professionnel net (€). Salarié : salaires APRÈS la déduction forfaitaire de 10 % ou les frais réels (art. 83 3°, auquel renvoie le 163 quatervicies II 1°) — ex. 60 000 € déclarés → 54 000 €. TNS/BNC : bénéfice imposable."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered; the description goes well beyond by disclosing the actual formulas, the PASS reference years (2025 = 47 100 €, 2026 = 48 060 €), floors and caps, and the legal sources used. It also flags the key behavioral trap (do not multiply this plafond by the TMI), which no annotation conveys.

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?

Dense but front-loaded: purpose first, then regime formulas, then the express limitation and the sibling redirect. The opening phrase is slightly redundant ('Plafond de déduction PER de l'année — Plafond de versement PER déductible du revenu de l'année'), and the parenthetical source list is long, but every other sentence earns its place.

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 read-only calculation tool with full parameter documentation, this covers regime selection, income base, year/PASS references, exclusions, legal sources and the misuse warning. The only minor omission is the shape of the returned value, which is partly addressed in the teaser parameter description.

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 each parameter already carries a detailed description (including the 10% abatement nuance on revenu_professionnel), so the schema does the heavy lifting. The description adds legal-regime framing and the 15% tranche context for TNS, but little parameter-level meaning beyond what the schema states.

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 resource and calculation: the deductible PER contribution ceiling for the year, split into two explicit regimes (salarié art. 163 quatervicies vs TNS/BNC art. 154 bis). It is immediately distinguishable from fiscal_per_gain, which the description explicitly demotes to a different job.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly scopes the tool as an 'express' version limited to a single income, excluding reliquats and spouse mutualisation, and states the when-not: it is a ceiling, not a tax saving — for the gain of a contribution use fiscal_per_gain. It even warns against multiplying by fiscal_tmi, naming the sibling that owns that operation.

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.