Skip to main content
Glama

Lexou · droit français

Calculer les intérêts au taux légal

calculer_interets_legaux
Read-onlyIdempotent

Décompte d'une créance : intérêts au taux légal semestre par semestre (taux publiés au Journal officiel depuis 2015), ou pénalités de retard entre professionnels, majoration de cinq points après une décision exécutoire. Rend le tableau des périodes, les taux appliqués et le total. Pas pour un taux d'usure ni un crédit à la consommation.

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>",
      "depuis": "<depuis>",
      "jusqua": "<jusqua>",
      "creancier": "<creancier>"
    },
    "name": "calculer_interets_legaux"
  }
}

Input Schema

NameRequiredDescriptionDefault
depuisYesPoint de départ : date de la mise en demeure, ou date d'échéance de la facture pour des pénalités
jusquaYesDate de fin du calcul (souvent aujourd'hui ou la date du paiement)
regimeNoPar défaut, intérêt au taux légal
montantYesSomme principale due, en euros
creancierYesLe créancier : particulier (taux des personnes physiques n'agissant pas pour des besoins professionnels) ou professionnel
taux_penalitesNoPour les pénalités entre professionnels
taux_contractuelNoTaux annuel en %, si taux_penalites vaut contractuel
decision_executoireNoDate à laquelle la condamnation est devenue exécutoire (majoration de cinq points deux mois après)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

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, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral context beyond them: the rate source and coverage window (Journal officiel rates since 2015), the duty increase rule tied to an enforceable decision, and the shape of the returned result (period table, applied rates, total). It does not discuss precision, rounding, or how partial semesters are split.

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?

Three dense sentences: capability first, output second, exclusion last — front-loaded and zero filler. Domain jargon is used precisely rather than explained, which is appropriate for a French legal-calculation tool.

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?

For an 8-parameter read-only calculator with no output schema, the description supplies the missing return-value description and the data-source limitation (JO rates from 2015). Combined with full schema coverage and safety annotations, an agent has everything needed to invoke it 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%, with three enums documented in-schema, so the parameters already explain themselves. The description reinforces the regime distinction and the purpose of the enforceable-decision date but does not add input formats, defaults, or interaction rules 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?

Opens with a specific verb+resource ('Décompte d'une créance : intérêts au taux légal') and immediately names the scope variants handled (semester-by-semester legal rates, professional late penalties, +5 point increase after an enforceable decision). It also states what it is not (taux d'usure, crédit à la consommation), so an agent can separate it from the other legal calculators in the sibling list without opening the schema.

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

Usage Guidelines4/5

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

The closing exclusion ('Pas pour un taux d'usure ni un crédit à la consommation') gives explicit when-not guidance, and the opening sentences establish when it applies (debt computation, professional penalties). It does not name a concrete alternative tool to route to, so it stops short of the when/when-not/alternatives trifecta.

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.

Resources