Skip to main content
Glama

simulateurs_demembrement_scpi

Read-onlyIdempotent

Démembrement de SCPI (nue-propriété / usufruit) — Projette un investissement en nue-propriété de SCPI (récupération de la pleine propriété au terme, aucun revenu pendant le démembrement) et l'usufruit correspondant (revenus nets d'IR, amortissement). IR branché sur le cIR de Qotien. Résultat ESTIMÉ. Pleine propriété au comptant → simulateurs_scpi ; à crédit → simulateurs_scpi_credit. (sources: Méthode financière standard (démembrement, actualisation) ; CGI (revenus fonciers de l'usufruitier) via cIR ; 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": "<montant>"
    },
    "name": "simulateurs_demembrement_scpi"
  }
}

Input Schema

NameRequiredDescriptionDefault
cleNoClé de démembrement — valeur de la nue-propriété en % (ex. 67).
dureeNoDurée du démembrement (années).
impotNoTaux d'imposition des revenus fonciers de l'usufruitier (%).
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
montantYesMontant investi en nue-propriété (€).
rendementNoRendement de la SCPI (% annuel).
valeur_partNoValeur d'une part (€).
revalorisationNoRevalorisation annuelle de la part (%).

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

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

Annotations already declare readOnly, idempotent and closed-world, so the description spends its credit on model behavior instead: no income during the démembrement, recovery of full ownership at term, tax treatment of the usufruitier's income via cIR, and that all market assumptions come from the caller. It does not mention the free 'teaser' preview or payment gating, 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?

The single paragraph is front-loaded with purpose, then mechanics, then sibling routing, then sources—good ordering with no filler sentences. The trailing sources parenthetical is slightly heavy but still earns its place as provenance for a financial estimate.

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?

For an 8-parameter simulation tool with no output schema, the description covers the modeling logic, the tax dependency, and the estimate caveat. It stops short of describing the shape of the returned figures (nue-propriété value, usufruit cash flows), which would be the last missing piece.

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 all eight parameters (cle, duree, impot, rendement, valeur_part, revalorisation, montant, teaser) are already documented in the schema itself. The description adds conceptual framing (the clé de démembrement, IR on usufruitier revenue) but no per-parameter meaning beyond what the schema states, so 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?

The description opens with a specific verb and resource ('Projette un investissement en nue-propriété de SCPI') and immediately explains the two legs modeled (nue-propriété and usufruit), so an agent can distinguish it from the plain SCPI simulators 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?

It explicitly routes the agent elsewhere with conditions: 'Pleine propriété au comptant → simulateurs_scpi ; à crédit → simulateurs_scpi_credit', and adds that results are ESTIMATED. The only minor gap is the absence of an explicit when-not-to-use statement, but the alternative mapping is unambiguous.

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.