Skip to main content
Glama

Kredi kartı asgari ödeme

kredi_karti_asgari_odeme_hesapla
Read-onlyIdempotent

Kredi kartı asgari ödemesini (limite göre BDDK oranı), eksik ödemede sonraki ekstreye yansıyacak faiz ve vergiyi, yalnız asgari ödenirse borcun kaç ayda kapanacağını hesaplar. Faiz boşsa TCMB azami oranı.

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": {
      "kartLimiti": "<kartLimiti>",
      "donemBorcu": "<donemBorcu>"
    },
    "name": "kredi_karti_asgari_odeme_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
donemBorcuYesTL.
kartLimitiYesTL.
odenenTutarNoSon ödeme tarihine kadar ödenen (TL). Boşsa asgari.
gecikilenGunNoSon ödeme tarihinden sonra geçen gün. Varsayılan 0.
aylikAkdiFaizNoAylık %, vergi hariç.
sabitAylikOdemeNoHer ay bu tutar ödenirse kapanma süresi de hesaplanır (TL).
aylikGecikmeFaiziNoAylık %, vergi hariç.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / aylikAkdiFaiz / description
      Previous value: -"Aylık akdi faiz (%), vergi hariç. Boşsa TCMB azami oranı."New value: +"Aylık %, vergi hariç."
    • changedInput schema / properties / aylikGecikmeFaizi / description
      Previous value: -"Aylık gecikme faizi (%), vergi hariç. Boşsa TCMB azami oranı."New value: +"Aylık %, vergi hariç."
    • changedInput schema / properties / donemBorcu / description
      Previous value: -"Ekstredeki dönem borcu (TL)."New value: +"TL."
    • changedInput schema / properties / gecikilenGun / description
      Previous value: -"Asgarinin altında ödendiyse son ödeme tarihinden sonra geçen gün. Varsayılan 0."New value: +"Son ödeme tarihinden sonra geçen gün. Varsayılan 0."
    • changedInput schema / properties / kartLimiti / description
      Previous value: -"Kart limiti (TL). Asgari ödeme oranı limite göre belirlenir."New value: +"TL."
    • changedInput schema / properties / odenenTutar / description
      Previous value: -"Son ödeme tarihine kadar ödenen tutar (TL). Boşsa asgari tutarın zamanında ödendiği varsayılır."New value: +"Son ödeme tarihine kadar ödenen (TL). Boşsa asgari."
    • changedInput schema / properties / sabitAylikOdeme / description
      Previous value: -"İsteğe bağlı: her ay sabit bu tutar ödenirse borcun kaç ayda kapanacağı da hesaplanır (TL)."New value: +"Her ay bu tutar ödenirse kapanma süresi de hesaplanır (TL)."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare a safe, read-only, idempotent, closed-world calculation, so the safety profile is covered. The description adds genuinely new behaviour: if the interest parameter is omitted, the TCMB maximum rate is applied, and the calculation includes tax (vergi) alongside interest on underpayment. It does not describe the shape of the returned result, but for a pure calculator that gap is minor.

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?

Two sentences, the first carrying all three computed outputs and the second the interest default. Nothing is padded, and the primary purpose is front-loaded. The first sentence is dense enough that the three outputs run together, but no words are wasted.

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?

For a stateless calculator with no output schema, the description covers everything an agent needs: what is computed, that tax is included, the underpayment consequence, the payoff-horizon calculation, and the default interest behaviour. No nested objects or enums exist to leave unexplained.

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 schema already explains each of the seven parameters including their units and defaults for odemenTutar and gecikilenGun. The description goes one step beyond by stating the fallback for a missing interest rate (TCMB azami oran), which is not documented in the schema for aylikAkdiFaiz — a small but real addition.

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?

The description names a specific verb-and-resource pair ('kredi kartı asgari ödemesini ... hesaplar') and enumerates three concrete computed outputs: the BDDK minimum payment ratio by limit, the interest-plus-tax carried to the next statement on underpayment, and the number of months to close the debt if only the minimum is paid. It is clearly distinct from other calculator siblings such as kredi_erken_kapatma_hesapla or kredi_hesapla in substance, but it never explicitly states that distinction, so a 5 is not warranted.

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?

The scenario is implied by content: the tool computes minimum payment, underpayment consequences, and payoff horizon. However, there is no explicit statement of when to choose this over the neighbouring credit tools (early payoff, general loan calculation), and no exclusions or prerequisites are given. It offers a default-behaviour hint for missing interest but no routing guidance.

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