Skip to main content
Glama

Calculate statutory late payment interest

calculate_late_interest
Read-onlyIdempotent

Calculates the statutory minimum interest on a late business payment. Euro area: ECB main refinancing rate on 1 January / 1 July of each half-year plus 8 percentage points, split by half-year, plus a fixed 40 EUR compensation (Directive 2011/7/EU); the ECB rate is loaded live. Sweden (SEK), Denmark (DKK), Poland (PLN) and Czechia (CZK): the national reference rate plus 8 points (Poland: 10) and the national fixed compensation (SEK 450, DKK 310, EUR 40/70/100 in PLN, at least CZK 1,200); in Czechia one rate for the whole delay. Switzerland: 5 % per year (Art. 104 OR). Hungary and Romania are not supported. Returns the formula, the rate for each period and the amounts. Contracts and national laws can differ.

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": {
      "amount": "<amount>",
      "due_date": "<due_date>",
      "country": "<country>"
    },
    "name": "calculate_late_interest"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesThe overdue amount in the national currency: EUR (euro area), SEK, DKK, PLN, CZK or CHF.
countryYesTwo-letter code of the country whose law applies, e.g. DE, SK, CH.
currencyNoOptional currency code; default the national currency (EUR in the euro area, SEK, DKK, PLN, CZK, CHF).
due_dateYesDue date of the invoice, YYYY-MM-DD. Interest runs from the next day.
payment_dateNoDate of payment, YYYY-MM-DD. Default: today.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"The overdue amount (EUR for euro area countries, CHF for Switzerland)."New value: +"The overdue amount in the national currency: EUR (euro area), SEK, DKK, PLN, CZK or CHF."
    • changedInput schema / properties / currency / description
      Previous value: -"Optional currency code; default EUR (euro area) or CHF (Switzerland)."New value: +"Optional currency code; default the national currency (EUR in the euro area, SEK, DKK, PLN, CZK, CHF)."
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world; the description adds the meaningful detail that the ECB rate is loaded live (explaining why output can vary over time) and that a fixed compensation component is included. It also notes the return content (formula, per-period rate, amounts), filling the gap left by the absent output schema. It does not address rounding or day-count conventions, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first sentence, but the rest is a dense semicolon-spliced enumeration of per-country rates and compensation caps that the tool itself returns as output. Some of that detail (e.g. SEK 450, DKK 310, CZK 1,200) does not help the agent decide or invoke, and the single-paragraph format makes it hard to scan.

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 six-parameter computation tool with no output schema, the description covers jurisdiction coverage, currency defaults and return contents, which is most of what an agent needs. Gaps remain around rounding, treatment of future due dates, and whether non-EU/non-listed countries simply fail, but these are secondary.

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 schema already documents all six parameters; the description nevertheless adds genuine meaning by mapping which country values trigger which rate regime and which national currency is the default for each. That reduces country/currency mismatches the agent could otherwise make from the two-letter code alone.

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?

States a specific verb and resource ('Calculates the statutory minimum interest on a late business payment') and immediately scopes it by jurisdiction, which cleanly separates it from the validation/verification siblings. An agent can tell this is the only computation tool in the catalog without opening any 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?

Gives clear applicability context: business payments, statutory minimum, per-country regimes, and explicitly names unsupported jurisdictions (Hungary and Romania), which prevents wasted calls. It adds the caveat that contracts and national laws can differ, signaling when the result is a floor rather than a definitive answer. No explicit use-instead-of-alternative sentence, but no sibling overlaps this function.

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