Skip to main content
Glama

simulateurs_rentabilite_reelle

Read-onlyIdempotent

Rentabilité réelle d'un placement (vrai TRI) — Calcule la rentabilité d'un placement à versements programmés en distinguant le VRAI TRI pondéré par le timing des flux (triReelPondere) du simple CAGR (rendement annualisé géométrique, qui ignore le timing). La valeur renvoyée est le vrai TRI. Résultat ESTIMÉ. (sources: Méthode financière standard (TRI/XIRR vs CAGR) ; Hypothèses fournies par l'appelant)

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_initial": "<versement_initial>",
      "valeur_actuelle": "<valeur_actuelle>"
    },
    "name": "simulateurs_rentabilite_reelle"
  }
}

Input Schema

NameRequiredDescriptionDefault
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
duree_moisNoDurée (mois).
frais_entreeNoFrais d'entrée (% par versement).
frais_gestionNoFrais de gestion (% / an).
valeur_actuelleYesValeur actuelle du placement (€).
versement_initialYesVersement initial (€).
versement_mensuelNoVersement mensuel (€).

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond them: the result is explicitly an ESTIMATE ('Résultat ESTIMÉ'), which metric is returned, and that hypotheses come from the caller — all relevant caveats for interpreting output.

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-loaded with the purpose and the key distinction (vrai TRI vs CAGR) in the first sentence, with the returned value stated early. Dense but every element earns its place; the parenthetical source list is minor padding.

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 7 parameters fully documented in the schema and no output schema, the description appropriately supplies the missing return-value information (the tool returns the true IRR figure) plus the estimation caveat. Only the absence of usage boundaries keeps it from being complete.

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%, so every parameter is already documented in the schema, including the teaser free-preview flag. The description adds no parameter-level detail (e.g. how frais_entree interacts with versement_mensuel), so the baseline 3 applies.

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 and resource ('Calcule la rentabilité d'un placement à versements programmés') and explicitly names the returned metric (le vrai TRI, triReelPondere) as distinct from CAGR. Sibling tools cover unrelated topics (SCPI, Girardin, fiscalité), so no explicit routing is needed, but the description never positions itself against 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?

Usage is implied by the resource: use it when you need a timing-weighted IRR for a placement with scheduled payments rather than a simple annualized return. There is no explicit when-not guidance, no mention of prerequisites, and no pointer to a sibling alternative.

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.