Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Calculer la déduction d'un versement PER

simulate_per
Read-onlyIdempotent

Calcule le disponible fiscal d'un versement PER (CGI art. 163 quatervicies), la part déductible, l'effet sur l'impôt sur le revenu et l'imposition de la part déduite à la sortie. Entrées : revenus professionnels, versement, tranche d'entrée, hypothèse de sortie. Sortie : disponible, part déductible, effet à l'entrée et à la sortie. La capitalisation n'est pas projetée. Calcul couvert par des cas de référence Marcel : résultat indicatif.

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": {
      "versement": "<versement>",
      "revenusProN1": "<revenusProN1>",
      "tmiEntree": "<tmiEntree>"
    },
    "name": "simulate_per"
  }
}

Input Schema

NameRequiredDescriptionDefault
tmiEntreeYesTMI actuelle en décimal (ex: 0.30)
versementYesMontant versé sur le PER
revenusProN1YesRevenus professionnels N-1
tmiSortieSaisieNoTMI estimée à la retraite (prioritaire)
pensionEstimeeAnnuelleNoPension annuelle pour estimation de la TMI de sortie

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description still adds real value: 'La capitalisation n'est pas projetée' discloses a modeling limitation, and 'résultat indicatif' plus the mention of reference cases signals the result's reliability status — neither is derivable from the annotations or schema.

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?

Front-loads the computation and its outputs in one dense sentence, then enumerates inputs and outputs and closes with the two caveats. Nearly every sentence earns its place, though the input/output enumeration slightly duplicates what the schema and the first sentence already convey.

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?

With no output schema, the description proactively names the returned figures (disponible, part déductible, effet à l'entrée et à la sortie), which is exactly what an agent needs. The remaining gap is the unresolved handling of the two optional exit-TMI parameters, a minor point for a read-only, deterministic calculation.

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 the schema already explains each of the 5 parameters including the 'prioritaire' note on tmiSortieSaisie. The description only restates the inputs at a conceptual level ('revenus professionnels, versement, tranche d'entrée, hypothèse de sortie') and does not clarify the precedence between tmiSortieSaisie and pensionEstimeeAnnuelle, so it adds little 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?

States a specific verb+resource: computes the fiscal capacity, deductible share, income-tax effect at entry, and taxation on exit of a PER contribution, with the legal basis (CGI art. 163 quatervicies) named. This clearly differentiates it from a pure exit-simulation sibling like simulate_per_sortie, though the overlap on 'imposition de la part déduite à la sortie' is never explicitly resolved.

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

Usage Guidelines3/5

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

The scope is implied by the input list (entry contribution, entry TMI, exit hypothesis), which suggests an entry-side deduction simulation. However, there is no explicit statement of when to use this versus simulate_per_sortie or simulate_remuneration_per, nor any stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Marcel 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