Skip to main content
Glama

simulateurs_scpi

Read-onlyIdempotent

SCPI au comptant — projection à terme — Projette un investissement en SCPI au comptant : valeur brute/nette de revente à terme, revenus distribués, TRI. Hypothèses de rendement, de revalorisation et de fiscalité fournies par l'appelant — résultat ESTIMÉ, non garanti. Achat à crédit → simulateurs_scpi_credit ; nue-propriété ou usufruit → simulateurs_demembrement_scpi. (sources: Méthode financière standard (actualisation de flux, TRI) ; 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": {
      "versement_initial": "<versement_initial>"
    },
    "name": "simulateurs_scpi"
  }
}

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).
fiscaliteNoTaux d'imposition des revenus fonciers (%, IR+PS agrégé).
duree_anneesNoHorizon (années).
frais_sortieNoFrais de sortie / décote de revente (%).
rendement_brutNoTaux de distribution brut annuel (%).
revalorisationNoRevalorisation annuelle de la part (%).
versement_initialYesVersement initial (€).
versement_mensuelNoVersement mensuel programmé (€).
reinvest_dividendesNoRéinvestir les dividendes.

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, idempotentHint and closed-world, so the safety profile is covered. The description adds real value beyond them: results are explicitly ESTIMÉ and non garanti, and all yield/revaluation/tax assumptions come from the caller rather than the tool. It does not discuss the meaning of the free 'teaser' preview path relative to a paid result, which is a residual gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then the output enumeration, then the estimation caveat, then sibling routing, then sources as a parenthetical. Every sentence carries distinct information; the leading label repeats the annotation title but is short and orients the reader immediately.

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 nine parameters and no output schema, the description compensates by naming the returned figures (valeur brute/nette, revenus distribués, TRI) and by flagging that results are estimates. The teaser/paid distinction is left to the schema, but otherwise the definition is sufficient to call the tool correctly.

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 one of the nine parameters is already documented at the field level. The description only restates that rendement, revalorisation and fiscalité are caller-supplied hypotheses, adding no syntax, units or interaction detail beyond the schema. Baseline 3 is appropriate.

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 investissement en SCPI au comptant') and enumerates the concrete outputs the agent will get: valeur brute/nette de revente, revenus distribués, TRI. It explicitly names the sibling simulations it is not (crédit, démembrement), so the tool is unambiguous within its family.

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?

Gives explicit routing rules with conditions: 'Achat à crédit → simulateurs_scpi_credit' and 'nue-propriété ou usufruit → simulateurs_demembrement_scpi'. The alternative and the condition selecting it are both stated, so the agent does not need to infer scope.

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.