Skip to main content
Glama

Cash-service.pl

Kalkulator kredytu (rata i koszt)

kalkulator_kredytu
Read-onlyIdempotent

Rata kredytu (równe albo malejące), suma odsetek i koszt całkowity dla kwoty, oprocentowania rocznego i liczby miesięcy; opcjonalnie pełny harmonogram spłaty. Używaj do pytań „jaka rata przy X zł na Y lat na Z %".

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>",
      "oprocentowanie": "<oprocentowanie>",
      "miesiace": "<miesiace>"
    },
    "name": "kalkulator_kredytu"
  }
}

Input Schema

NameRequiredDescriptionDefault
typNoRodzaj rat: rowne (annuitetowe) albo malejacerowne
kwotaYesKwota kredytu PLN
miesiaceYesLiczba rat (1–600)
harmonogramNoDołącz pełny harmonogram miesięczny (długi wynik) - tylko gdy użytkownik o niego prosi
oprocentowanieYesOprocentowanie roczne w %, np. 7.2

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, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism need no restating. The description adds that a full repayment schedule is optional and implies a long output, but says nothing about rounding, whether fees/commissions are included, or result units beyond PLN in the schema. Useful but thin beyond the annotations.

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?

One front-loaded sentence enumerating outputs, one clarifying the optional schedule, one usage example. No filler, no repetition of the title, and the most decision-relevant information comes first.

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?

There is no output schema, and the description does compensate by naming the returned figures (installment, interest total, total cost) and the optional schedule. Remaining gaps are minor: no statement of result currency/rounding or whether early-repayment or fee assumptions exist.

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 all five parameters, the enum values rowne/malejace and the 1–600 month bound are already documented. The description restates the equal-vs-decreasing distinction and the three required inputs, adding no format or interpretation detail the schema lacks. 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?

Names the exact outputs (rata, suma odsetek, koszt całkowity) and the exact inputs (kwota, oprocentowanie roczne, liczba miesięcy), plus the two installment variants. That is specific enough to separate it from every listed sibling, all of which are tax/HR/geo calculators rather than loan math.

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 final sentence gives a concrete trigger pattern ("jaka rata przy X zł na Y lat na Z %"), and the description notes the schedule is only returned optionally. It stops short of stating when NOT to use it (e.g. no mention of how it relates to other financial calculators), so it is clear context without exclusions.

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