Skip to main content
Glama

simulateurs_apport_credit

Read-onlyIdempotent

Arbitrage apport vs crédit (3 stratégies) — Compare trois stratégies de financement d'un projet immobilier : tout apporter, apport minimal + placement d'un bien secondaire, apport minimal + placement financier. Rend l'effort mensuel et le patrimoine/flux de trésorerie à terme de chaque stratégie. Résultat ESTIMÉ. (sources: Méthode financière standard (mensualités, capitalisation) ; Hypothèses de rendement/durée 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": {
      "projet": "<projet>",
      "apport": "<apport>"
    },
    "name": "simulateurs_apport_credit"
  }
}

Input Schema

NameRequiredDescriptionDefault
apportYesApport disponible (€).
projetYesMontant total du projet (€).
teaserNoAperçu gratuit, sans paiement : true renvoie le chiffre de tête avec sa confiance et ses sources (free preview, no payment).
uniqueNoStratégie « tout apporter » : { apport, rendement, duree, tauxPret }. Défauts moteur si absent.
financierNoStratégie « placement financier » : { apport, rendement, duree, tauxPret }.
secondaireNoStratégie « bien secondaire » : { apport, rendement, duree, tauxPret }.

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.6/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 and the description instead adds the important caveat that the result is ESTIMÉ with named sources (standard financial method plus caller-supplied return/duration assumptions). It also discloses what is returned per strategy (monthly effort, patrimoine and cash flow at term), though it says nothing about precision, edge cases, or how assumptions propagate when optional strategy objects are omitted.

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 content is front-loaded: title-style opening, then the three-strategy enumeration, then return values, then the estimation disclaimer and sources. The parenthetical source block is dense but each element (method, caller-supplied hypotheses) carries useful meaning; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with nested strategy objects and no output schema, the description does describe the shape of results and the caller-supplied assumptions, which is the critical piece. It leaves gaps on defaults for omitted strategy objects, units beyond the schema, and how the teaser preview relates to the paid full result, so it is adequate but not fully self-sufficient.

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% and the nested objects are documented in the schema, so the baseline is 3. The description adds a little by stating that rendement/durée hypotheses come from the caller, which clarifies the meaning of the nested strategy objects, but it does not explain the interaction between the top-level apport/projet and the per-strategy apport fields.

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?

The description names a concrete verb ('Compare') and enumerates the three specific strategies (tout apporter, apport minimal + bien secondaire, apport minimal + placement financier), so the agent knows exactly what computation happens. It does not state how this differs from adjacent simulateurs (e.g. simulateurs_scpi_credit), so it falls short of full sibling differentiation.

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 rather than stated: the framing 'Arbitrage apport vs crédit' signals a real-estate financing decision, and the three listed strategies indicate the scenario space. There is no explicit when-to-use/when-not guidance, no prerequisites, and no pointer to an alternative tool for related credit or SCPI simulations.

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.