Skip to main content
Glama

simulateurs_rente_viagere

Read-onlyIdempotent

Rente viagère à titre onéreux (nette d'impôt) — Estime la rente viagère servie contre l'aliénation d'un capital : rente brute (via l'espérance de vie), part imposable selon l'âge d'entrée en jouissance (art. 158, 6° CGI), surcoût d'IR (via le cIR de Qotien) et rente nette mensuelle. Espérance de vie bornée 60–80 ans. Résultat ESTIMÉ. (sources: CGI art. 158, 6° (abattement rente viagère à titre onéreux) via cIR ; Table d'espérance de vie (INSEE, bornée 60–80 ans))

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": {
      "age": "<age>",
      "montant": "<montant>"
    },
    "name": "simulateurs_rente_viagere"
  }
}

Input Schema

NameRequiredDescriptionDefault
ageYesÂge d'entrée en jouissance (60–80).
sexeNoSexe (table d'espérance de vie).homme
partsNoParts de quotient familial.
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
montantYesCapital aliéné (€).
frais_arrerageNoFrais sur arrérages (%).
taux_actualisationNoTaux d'actualisation (%).
revenu_net_imposableNoRevenu net imposable du foyer hors rente (€) — sert au cIR.

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. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds genuinely useful behavior beyond them: the result is explicitly an ESTIMATE, life expectancy is bounded to 60–80 years, and the underlying sources (CGI art. 158, 6°, INSEE table, cIR) are disclosed. It does not address rate limits or the payment/preview mechanics, which keeps it from a 5.

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: the resource and estimate come first, the calculation chain second, and the source list is properly relegated to a trailing parenthetical. Some of the parenthetical legal sourcing is redundant with the annotations title, but nothing is genuinely wasteful.

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?

With no output schema, the description must carry the return shape and it does — it names all four returned figures. Combined with 100% schema coverage on 8 parameters and annotations covering the read-only profile, an agent has everything needed to call this correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description earns above that by linking parameters to model mechanics — age drives the 'part imposable' and the bounded life-expectancy table, and household income feeds the cIR-based 'surcoût d'IR'. It still does not explain how frais_arrerage or taux_actualisation affect the result.

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 precise verb and resource ('Estime la rente viagère servie contre l'aliénation d'un capital') and enumerates the exact outputs (rente brute, part imposable, surcoût d'IR, rente nette mensuelle). The legal framing ('à titre onéreux', art. 158, 6° CGI) makes it unmistakably distinct from the fiscal_* and retraite_* siblings without needing to name them.

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 scenario of use is implied by the described computation (converting a capital into a life annuity), but there is no explicit when-to-use vs. alternative statement, no prerequisites, and no mention of when a different simulator would be appropriate. The teaser parameter hints at a free/paid split but the description never explains it.

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.