Skip to main content
Glama
Sign In

Marcel

by fr.marcel-retraite
OverviewDiscussionsAdmin

Calculer un rachat de trimestres

simulate_rachat
Read-onlyIdempotent

Calcule le coût d'un rachat de trimestres (versement pour la retraite) au barème de la CNAV 2026 et le supplément de pension correspondant. Entrées : âge, revenu, nombre de trimestres, option. Sortie : coût brut, coût après déduction, supplément de pension annuel (gainPensionAnnuel). 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": {
      "ageRachat": "<ageRachat>",
      "revenuAnnuelMoyen": "<revenuAnnuelMoyen>",
      "option": "<option>",
      "nbTrimestres": "<nbTrimestres>"
    },
    "name": "simulate_rachat"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionYestaux_seul : améliore le taux ; taux_et_duree : allonge aussi la durée
ageRachatYesÂge au moment du versement
nbTrimestresYesNombre de trimestres à racheter
trimestresRequisNoDurée requise pour la génération (défaut 172)
revenuAnnuelMoyenYesRevenu annuel moyen — détermine la tranche A/B/C
salaireAnnuelMoyenNoSalaire moyen (mode proxy si pension inconnue)
trimestresManquantsNoTrimestres manquants pour le taux plein
pensionAnnuelleEstimeeNoPension annuelle estimée (mode exact)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds valuable context beyond that: the calculation uses the CNAV 2026 barème, returns cost before/after deduction, and explicitly warns that the result is indicative (résultat indicatif).

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 compact sentences, front-loaded with the verb and calculation scope, then inputs, outputs, and a caveat. The input/output enumeration partially repeats the schema, but it is short enough to earn its place.

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 eight parameters and no output schema, the description usefully names the main return values (coût brut, coût après déduction, gainPensionAnnuel) and flags the result as indicative. It stops short of explaining the optional proxy/exact mode and defaults, which an agent must infer from the schema.

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 documents all eight parameters in detail. The description lists only four inputs (âge, revenu, nombre de trimestres, option) and says nothing about the optional exact-vs-proxy mode or the trimestresRequis/trimestresManquants/salaireAnnuelMoyen/pensionAnnuelleEstimee fields. Baseline 3 applies when the schema carries the semantic load.

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 specific verb (Calcule), resource (coût d'un rachat de trimestres / versement pour la retraite), and scope (barème CNAV 2026 plus the pension supplement). This is unmistakably distinct from the other simulate_* siblings, which cover PER, AV, CTO, immo, etc.

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?

Usage is implied by the domain: use this when estimating the cost of a quarterly buyback. There is no explicit when-to-use/when-not guidance, no mention of prerequisites, and no named alternative for related retirement scenarios. The closing note about Marcel reference cases describes reliability, not selection.

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