Skip to main content
Glama
OpenLMNP

OpenLMNP

Compute Loan Schedule

compute_loan_schedule
Destructive

Generates or regenerates a real estate loan amortization schedule by recalculating capital, interest, and insurance for each monthly payment, while protecting bank-imported schedules unless forced.

Instructions

Génère (ou régénère) le tableau d'amortissement théorique d'un emprunt immobilier. Supprime les échéances existantes et recalcule toutes les mensualités (capital, intérêts, assurance). Un emprunt dont les échéances ont été importées depuis le tableau de la banque est protégé : utilisez force=true pour l'écraser volontairement. Retourne un résumé financier ainsi que la première et la dernière échéance. Tous les montants sont en euros.

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": {
      "loan_id": "<loan_id>"
    },
    "name": "compute_loan_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoÉcraser volontairement un tableau d'amortissement importé depuis la banque (défaut : false)
loan_idYesIdentifiant de l'emprunt à recalculer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.1
    • addedInput schema / properties / force
      Added value: +{
      +  "description": "Écraser volontairement un tableau d'amortissement importé depuis la banque (défaut : false)",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / loan_id / description
      Added value: +"Identifiant de l'emprunt à recalculer"
  2. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Beyond destructiveHint=true, the description discloses exactly what is destroyed ("Supprime les échéances existantes"), what is recomputed (capital, intérêts, assurance), the protection rule for bank-imported loans, and the shape of the result (résumé financier plus first and last installment). This is the kind of mutation detail annotations cannot convey.

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?

Five tight sentences, ordered from what it does, to what it destroys, to the exception, to the return value, to the unit. Nothing is repeated from the schema and nothing is filler.

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?

There is no output schema, and the description compensates by describing the return value and the currency of all amounts. For a two-parameter destructive tool, an agent has everything needed to call it correctly or avoid it.

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, but the description adds real meaning for force by explaining the protection mechanism it bypasses and framing the override as deliberate. loan_id gets no elaboration beyond the schema, which keeps it short of a 5.

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?

"Génère (ou régénère) le tableau d'amortissement théorique d'un emprunt immobilier" gives a specific verb (generate/regenerate) and resource (amortization schedule for a real-estate loan). The mention that it deletes existing installments and recalculates everything clearly separates it from the read-only sibling get_loan_schedule.

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 states when the tool applies (regenerating a theoretical schedule), names the blocking condition (a loan whose installments were imported from the bank is protected), and gives the explicit escape hatch: "utilisez force=true pour l'écraser volontairement". When-to-use and when-blocked are both spelled out.

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