Skip to main content
Glama

Kredi erken kapatma

kredi_erken_kapatma_hesapla
Read-onlyIdempotent

Kredi erken kapatılınca ödenecek tutarı, kurtulunan faizi ve konut kredisinde erken ödeme tazminatını hesaplar.

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": {
      "kalanVadeAy": "<kalanVadeAy>",
      "aylikTaksit": "<aylikTaksit>",
      "aylikFaiz": "<aylikFaiz>"
    },
    "name": "kredi_erken_kapatma_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
turNoVarsayılan ihtiyac-tasit.
faizTipiNoKonut kredisinde. Varsayılan sabit.
aylikFaizYesAylık faiz (%).
aylikTaksitYesTL.
kalanVadeAyYesKalan taksit sayısı.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / aylikFaiz / description
      Previous value: -"Kredinin aylık faiz oranı (%)."New value: +"Aylık faiz (%)."
    • changedInput schema / properties / aylikTaksit / description
      Previous value: -"Aylık taksit tutarı (TL)."New value: +"TL."
    • changedInput schema / properties / faizTipi / description
      Previous value: -"Konut kredisinde faiz tipi. Varsayılan sabit."New value: +"Konut kredisinde. Varsayılan sabit."
    • changedInput schema / properties / kalanVadeAy / description
      Previous value: -"Kalan taksit sayısı (ay)."New value: +"Kalan taksit sayısı."
    • changedInput schema / properties / tur / description
      Previous value: -"Kredi türü. Varsayılan ihtiyac-tasit."New value: +"Varsayılan ihtiyac-tasit."
  2. 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=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is fully covered structurally. The description adds little beyond that: it names the computed values but does not state assumptions, rounding/currency conventions, or that the housing compensation applies only when tur=konut. Adequate but not rich.

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?

A single sentence, front-loaded with the triggering condition and then the three outputs; no filler, no repetition of the title. Every clause carries information an agent needs.

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 compensates by enumerating what the tool returns (payable amount, interest saved, compensation), which is the key thing an agent cannot learn from structured fields. It does not describe the response shape or units, a minor gap for a low-complexity, fully documented 5-parameter calculator.

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%, with enums and defaults documented inline (tur defaults to ihtiyac-tasit, faizTipi applies to konut loans and defaults to sabit), so the baseline is 3. The description adds no parameter-level meaning beyond echoing the housing-loan context already present in the schema.

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?

The description names a specific verb ('hesaplar') and three concrete outputs: the amount payable on early payoff, the interest saved, and the early-payment compensation specific to housing loans. This separates it clearly from the sibling kredi_hesapla (general loan calculation) without needing to name it.

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 framing 'kredi erken kapatılınca' establishes the scenario that selects this tool (early closure, not regular installment planning), and the mention of 'konut kredisinde erken ödeme tazminatı' signals the housing-loan case. It stops short of explicit when-not guidance or naming an alternative calculator for non-early-payoff questions.

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