Skip to main content
Glama

Kalkulator B2B

Harmonogram kredytu

loan_schedule
Read-only

Harmonogram spłaty kredytu (hipotecznego, konsumenckiego albo firmowego) przy STAŁYM oprocentowaniu podanym w argumentach: raty równe (annuitetowe) albo malejące, opcjonalnie nadpłata jednorazowa i/lub co miesiąc — z obniżeniem raty albo ze skróceniem okresu — i rekompensata za nadpłatę ze stawki z umowy, z limitami ustawowymi kredytu hipotecznego (art. 40 ustawy o kredycie hipotecznym) i konsumenckiego (art. 49 ustawy o kredycie konsumenckim); obie ustawy chronią tylko konsumentów, więc kredytu firmowego (na działalność) nie obejmują — wtedy wiąże wyłącznie umowa. Zwraca pierwszą i ostatnią ratę, odsetki i kwotę zapłaconą razem, liczbę rat oraz podsumowanie rok po roku (kapitał, odsetki, saldo). Nie prognozuje WIBOR-u ani POLSTR-u i nie ocenia zdolności kredytowej — nie mówi, ile bank pożyczy. Raty równe i malejące porównasz, wywołując narzędzie dwa razy.

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": {
      "principal": "<principal>",
      "annualRatePct": "<annualRatePct>",
      "months": "<months>",
      "installmentType": "<installmentType>"
    },
    "name": "loan_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsYesLiczba rat miesięcznych, 1–420
principalYesKwota kredytu (saldo do spłaty na start harmonogramu), zł
overpaymentNoNadpłata: jednorazowa (oneTime) i/lub co miesiąc (monthly), z trybem
annualRatePctYesOprocentowanie nominalne roczne w procentach (0–30), stałe przez cały harmonogram
installmentTypeYesequal = raty równe (annuitetowe), decreasing = raty malejące (stała część kapitałowa)
earlyRepaymentFeePctNoRekompensata za wcześniejszą spłatę ze stawki w umowie, % nadpłacanej kwoty. Bez wartości opłata nie jest liczona. Przy kredycie konsumenckim bank może żądać najwyżej 1% (0,5% w ostatnim roku umowy, art. 49 ustawy o kredycie konsumenckim); przy kredycie firmowym (na działalność) wiąże tylko umowa

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare a safe read-only, non-destructive, closed-world operation; the description goes well beyond that by naming the returned values (first and last installment, interest, total paid, installment count, year-by-year capital/interest/balance breakdown) and by explaining how statutory early-repayment caps apply to mortgage and consumer loans but not to business loans, where only the contract governs.

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

Conciseness4/5

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

Purpose and scope are front-loaded in the opening clause, and every sentence carries information (scope, outputs, limits, alternatives). The dense semicolon-and-dash chain, especially the statutory exposition, makes it harder to scan than it needs to be.

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?

With no output schema and nested overpayment objects, the description must carry both return-value and scope burden, and it does: output contents are enumerated, assumptions (fixed rate, monthly installments) are stated, and the legal limitation context is supplied. An agent could call this correctly without further information.

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%, so parameters are already documented; the description mostly restates them (fixed rate, equal vs decreasing, overpayment with lowering installment vs shortening term). The legal framing around the early-repayment compensation fee adds real meaning, but the contract-vs-statute distinction has no corresponding loan-type parameter, so it stays informational rather than operational.

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+resource: builds a loan repayment schedule for a fixed rate given in the arguments, with equal or decreasing installments plus optional one-time/monthly overpayments. It also bounds the scope explicitly (fixed rate only, no WIBOR/POLSTR forecasting, no creditworthiness assessment), which separates it cleanly from advisory or rate-lookup siblings.

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 concrete usage context: compare equal vs decreasing installments by calling the tool twice, and clarifies what the tool will not answer (how much the bank will lend, floating-rate forecasts). It lacks explicit 'when not to use / use X instead' routing, but no close sibling overlaps enough to require it.

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