Skip to main content
Glama
OpenLMNP

OpenLMNP

Create Loan

create_loan
Destructive

Creates a real estate loan for an LMNP property and generates its theoretical amortization schedule, including fees and insurance options.

Instructions

Crée un emprunt immobilier pour un bien LMNP et génère son tableau d'amortissement théorique. Les montants (amount, monthly_payment, insurance_monthly, fees_amount, early_repayment_amount) sont en euros. fees_spread_method ne joue que si l'étalement des frais est activé depuis le profil : linear (fractions égales, défaut) ou interest (prorata des intérêts courus, BOI-BIC-CHG-20-30-40 § 100-110).

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": {
      "property_id": "<property_id>",
      "amount": "<amount>",
      "annual_rate": "<annual_rate>",
      "duration_months": "<duration_months>",
      "start_date": "<start_date>"
    },
    "name": "create_loan"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesCapital emprunté en euros
bank_nameNoNom de la banque
start_dateYesDate de la 1ère échéance (Y-m-d)
annual_rateYesTaux nominal annuel en % (ex : 1.5 pour 1,5 %)
fees_amountNoFrais d'emprunt en euros : dossier, courtage, part non restituable d'une caution (art. 39-1-1° quater CGI)
property_idYesIdentifiant du bien immobilier
fees_paid_onNoDate de paiement des frais (Y-m-d). Absent = start_date
is_dedicatedNoEmprunt dédié à 100 % au logement loué, sans quote-part (défaut : false)
insurance_rateNoTaux annuel de l'assurance en %, si insurance_type=variable
insurance_typeNofixed (montant fixe mensuel, défaut) ou variable (taux sur capital restant dû)
duration_monthsYesDurée totale en mois (ex : 240 pour 20 ans)
monthly_paymentNoMensualité hors assurance en euros. Absent ou 0 = calcul automatique
insurance_monthlyNoMontant mensuel de l'assurance en euros, si insurance_type=fixed
fees_spread_methodNoMéthode d'étalement SI l'option est activée dans le profil : linear (fractions égales, défaut) ou interest (prorata des intérêts courus, nécessite un tableau d'amortissement)
early_repayment_dateNoDate d'un remboursement anticipé déjà survenu (Y-m-d), le cas échéant
early_repayment_amountNoCapital remboursé par anticipation à cette date, en euros (total du capital restant dû pour un remboursement intégral)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations only supply destructiveHint=true, so the description carries the rest of the burden. It usefully discloses a write side effect (schedule generation) and a conditional branch tied to a profile-level setting, but says nothing about validation failures, duplicate loans, or what happens to the generated schedule afterwards.

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?

Three sentences, front-loaded with purpose and side effect, with no filler. The enumeration of euro amounts is the weakest sentence since the schema already states 'en euros' per field.

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 16-parameter mutation with no output schema, the description should say what is returned (the loan record, the schedule, or both) and whether the schedule is persisted. Purpose and conditional logic are covered, but the return contract is left to inference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description nonetheless adds real meaning by clarifying that fees_spread_method is inert unless fee spreading is enabled in the profile, and by citing the legal reference governing the 'interest' method. The list of euro-denominated fields is largely redundant with the schema.

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?

States a specific verb and resource ('Crée un emprunt immobilier pour un bien LMNP') plus the side effect of generating a theoretical amortization schedule. It does not, however, differentiate itself from the sibling compute_loan_schedule, which sounds like it produces a similar artifact.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as compute_loan_schedule or update_loan. The agent must infer from the name alone that this persists a new loan rather than simulating one.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.