Skip to main content
Glama

simulateurs_scpi_credit

Read-onlyIdempotent

SCPI à crédit — effort d'épargne et TRI — Projette une SCPI financée à crédit : mensualité, effort d'épargne, fonds propres et TRI à terme (intérêts + assurance déductibles). Résultat ESTIMÉ (hypothèses de rendement/revalorisation/taux). Achat au comptant → simulateurs_scpi ; nue-propriété ou usufruit → simulateurs_demembrement_scpi. (sources: Méthode financière standard (tableau d'amortissement, TRI de flux) ; Hypothèses de marché 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": {
      "montant_credit": "<montant_credit>"
    },
    "name": "simulateurs_scpi_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
apportNoApport initial (€).
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
taux_creditNoTaux du crédit (% annuel).
taux_revenuNoTaux de distribution SCPI (% annuel).
duree_anneesNoDurée du crédit (années).
montant_creditYesMontant emprunté (€).
taux_assuranceNoTaux d'assurance emprunteur (% du capital / an).
taux_impositionNoTaux d'imposition des revenus (%).
taux_revalorisationNoRevalorisation annuelle (%).

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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and idempotentHint=true, so the safety profile is covered. The description adds real context beyond them: results are ESTIMATED from caller-supplied yield/revaluation/rate assumptions, and interest plus borrower insurance are treated as deductible in the TRI. It does not explain the teaser/free-preview behavior, but that is documented in the 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-loaded with the title-purpose, then outputs, then the estimate caveat, then routing to alternatives, then provenance. Dense but every element carries information; the sources parenthetical is mildly verbose but justifies the hypothesis-driven nature of the numbers.

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 9 parameters, no output schema and no nested objects, the description compensates by naming exactly what the calculation returns (mensualité, effort d'épargne, fonds propres, TRI) and warning that the result is an estimate dependent on caller assumptions. Nothing essential to calling or interpreting it is missing.

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, and the baseline is 3. The description only loosely signals which inputs matter by naming the outputs and the deductibility of interest and insurance (relating to taux_imposition), without adding format or range guidance beyond the schema.

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 une SCPI financée à crédit') and enumerates the computed outputs: mensualité, effort d'épargne, fonds propres, TRI. It explicitly names the two sibling tools covering the adjacent cases (comptant, démembrement), so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Routes the agent explicitly: cash purchase → simulateurs_scpi, nue-propriété/usufruit → simulateurs_demembrement_scpi, leaving this tool for the leveraged case. Both the when-to-use and the when-to-use-something-else conditions are stated.

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.