Skip to main content
Glama

TenderWatch, marchés publics

Calculer les intérêts moratoires

calculer_interets_moratoires
Read-only

Calcule les intérêts moratoires et l'indemnité de 40 € dus par un acheteur public qui a payé une facture en retard (taux BCE + 8 points, code de la commande publique).

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_ttc": "<montant_ttc>",
      "date_reception_facture": "<date_reception_facture>",
      "date_paiement": "<date_paiement>"
    },
    "name": "calculer_interets_moratoires"
  }
}

Input Schema

NameRequiredDescriptionDefault
montant_ttcYesMontant TTC de la facture, en euros.
date_paiementYesAAAA-MM-JJ, date du paiement effectif.
type_acheteurNoDétermine le délai (30, 50 ou 60 jours). Défaut : État ou collectivité.
date_reception_factureYesAAAA-MM-JJ.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful substance beyond that: the calculation basis (BCE rate + 8 points) and the legal source (code de la commande publique). It does not say what the response contains or how the delay period is derived.

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?

A single dense sentence that front-loads the computation and its scope, with zero filler. Every clause (indemnité, late payment, rate formula, legal basis) carries information.

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 a pure, side-effect-free calculation with no annotations burden beyond readOnly and no output schema, the description covers purpose, legal basis and inputs well. It is only slightly short of complete in not hinting at the returned values (interest amount, days late, indemnité).

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 coverage is 100%, so every parameter including the enum and its default is documented in the schema. The description adds no syntax or format detail for the four inputs, so the 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?

Specific verb ('Calcule') plus precise resources (intérêts moratoires and the 40 € indemnité), scoped to late payment by a public buyer. Nothing overlaps with the sibling tools (definitions, procedure thresholds, tender search), so an agent can select it unambiguously.

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 description clearly names the triggering situation — a public buyer who paid an invoice late — which is enough context to know when to call it. It does not state exclusions or point to a sibling for adjacent needs, so it stops short of a 5.

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