Skip to main content
Glama

simulateurs_private_equity

Read-onlyIdempotent

Private Equity — échéancier appels/distributions (courbe en J) — Projette un fonds de Private Equity sur un échéancier type (8 appels de capital puis 10 distributions) : total appelé, total distribué, DPI/TVPI et TRI daté des flux (XIRR). Résultat ESTIMÉ (échéancier et montants théoriques). (sources: Méthode financière standard (courbe en J, XIRR) ; Échéancier type fourni par défaut)

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": {
      "montant_initial": "<montant_initial>"
    },
    "name": "simulateurs_private_equity"
  }
}

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).
multipleNoTVPI cible : total distribué = multiple × montant appelé (hypothèse de performance ; 1,6 = +60 %).
date_debutNoDate de départ (AAAA-MM-JJ) pour dater les flux.2025-01-01
montant_initialYesEngagement / montant initial (€).

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.1/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 description's job is to add modeling context — and it does: it discloses the fixed schedule (8 capital calls, then 10 distributions), the standard J-curve/XIRR methodology, and crucially that the result is ESTIMATED with theoretical amounts. That caveat is behaviorally important and not derivable from any structured field.

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?

A single dense sentence front-loads the resource and the modeling approach before the output list, followed by a short estimate disclaimer and a source parenthetical. Every element earns its place, though the source note is marginally informational rather than operational.

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 must convey what comes back — it does, naming the four computed indicators. Combined with the estimate disclaimer and the fixed-schedule assumption, an agent has enough to call it and interpret results; only the teaser/preview distinction is left to 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 description coverage is 100%, so each parameter (teaser, multiple, date_debut, montant_initial) is already documented with defaults, units and meaning. The description adds no parameter-level detail beyond what the schema provides, so the baseline 3 applies.

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 verb and resource: 'Projette un fonds de Private Equity sur un échéancier type (8 appels de capital puis 10 distributions)', then enumerates the outputs produced (total appelé, total distribué, DPI/TVPI, TRI/XIRR). No sibling in the catalog covers private equity fund cash flows, and the description makes that domain boundary unmistakable.

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

Usage Guidelines4/5

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

The use case is clear from the text: project a PE fund subscription under a standard 8-call/10-distribution schedule. It does not name exclusions or point to alternative tools, but the sibling set (fiscal_*, retraite_*, referentiel_*) does not overlap, so the risk of misselection is low.

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.