Skip to main content
Glama

Prawnet: Polish case law and legislation

Kalkulator odsetek

odsetki
Read-onlyIdempotent

Odsetki od kwoty za okres (jak kalkulatory prawnet.pl, bez bazy danych). typ: za_opoznienie (art. 481 k.c.), ustawowe — kapitałowe (art. 359 k.c.), handlowe i handlowe_podmiot_leczniczy (ustawa o przeciwdziałaniu nadmiernym opóźnieniom w transakcjach handlowych), maksymalne i maksymalne_za_opoznienie (dwukrotność ustawowych), umowne i umowne_za_opoznienie (stopa z umowy ograniczona do maksymalnych; opcjonalnie kapitalizacja roczna), podatkowe, podatkowe_obnizone, podatkowe_podwyzszone, oplata_prolongacyjna (Ordynacja podatkowa; zaokrąglenie do pełnych złotych, próg minimalny). Odsetki proste: kwota × stawka × dni / 365, obie daty włącznie, rozbicie na okresy zmian stawek (tabele od 1.01.2016). Wynik: odsetki, suma z kwotą główną, okresy ze stawkami, aktualna stawka, podstawa_prawna, stan_prawny (data weryfikacji stawek), zrodla_stawek, link do kalkulatora. Wynik orientacyjny, nie porada prawna.

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": {
      "kwota": "<kwota>",
      "od": "<od>"
    },
    "name": "odsetki"
  }
}

Input Schema

NameRequiredDescriptionDefault
doNoOstatni dzień naliczania, włącznie, RRRR-MM-DD (np. dzień zapłaty); domyślnie dziś
odYesPierwszy dzień naliczania, włącznie, RRRR-MM-DD (zwykle dzień po terminie płatności); najwcześniej 2016-01-01
typNoDomyślnie za_opoznienie. ustawowe = kapitałowe (art. 359 § 2 k.c.); handlowe_podmiot_leczniczy = stopa + 8 p.p.
kwotaYesKwota główna (zaległość) w zł
stopaNoTypy umowne: stopa z umowy, % rocznie
data_decyzjiNooplata_prolongacyjna: dzień decyzji o odroczeniu / rozłożeniu na raty, RRRR-MM-DD; domyślnie dzień przed od
kapitalizacja_rocznaNoTypy umowne: roczna kapitalizacja (domyślnie brak)

Output Schema

NameRequiredDescriptionDefault
statusNo
citationsNo
wersja_danychNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Goes well beyond the annotations, which only cover read-only/idempotent/non-destructive/closed-world. The description discloses the exact formula (kwota × stawka × dni / 365), that both dates are inclusive, that results are broken down into periods of changing rates using tables from 1.01.2016, that umowne rates are capped at the maximum, that oplata_prolongacyjna rounds to whole złoty with a minimum threshold, and that the result is orientacyjny and not legal advice.

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?

Front-loaded with the core purpose, and every type entry carries legal content, so little is pure filler. However, it is a single dense run-on paragraph, and the closing list of result fields duplicates what the output schema already provides.

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 7-parameter, 12-value enumerated calculator, the description covers formulas, date semantics, rounding, defaults, legal bases, and a disclaimer; the presence of an output schema means the result-field listing is surplus rather than necessary. The remaining gap is relational: it never positions itself against the other calculation tools in the catalog.

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, and the description does add meaning: it identifies which types consume 'stopa' (umowne types, capped at the maximum), that roczna kapitalizacja applies only to umowne types, that data_decyzji is specific to oplata_prolongacyjna, and that the default typ is za_opoznienie. The day-count convention stated for the tool also clarifies the date parameters.

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 operation and resource: interest on an amount for a period, computed like prawnet.pl calculators, with an explicit 'bez bazy danych' (no database) qualifier. The enumeration of twelve interest types makes the scope unmistakable. It does not, however, distinguish itself from related calculator siblings such as policz, koszty_zastepstwa, or oplata_sadowa.

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

Usage Guidelines3/5

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

Guidance is strong at the parameter level — each 'typ' value is tied to its legal basis (art. 481 k.c., art. 359 k.c., ustawa o przeciwdziałaniu nadmiernym opóźnieniom), which effectively tells an agent which mode fits which situation. But at the tool level there is no explicit when-to-use or when-not, and no alternative tool is named despite several calculator-like siblings.

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