Skip to main content
Glama

Kredi taksiti

kredi_hesapla
Read-onlyIdempotent

Eşit taksitli kredinin taksitini, toplam ödemesini, faizini ve türüne göre BSMV/KKDF vergisini 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": {
      "tutar": "<tutar>",
      "aylikFaiz": "<aylikFaiz>",
      "vadeAy": "<vadeAy>"
    },
    "name": "kredi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
turNoVarsayılan ihtiyac-tasit.
tutarYesTL.
vadeAyYesAy.
aylikFaizYesAylık faiz (%), ör. 3,5.
mevcutKonutNoKonut kredisi: üzerine kayıtlı konut/hisse var mı (yok ise BSMV istisnası). Varsayılan belirsiz.
konutFinansmaniNoKonut kredisi: konut finansmanı niteliğinde mi (KKDF istisnası). Varsayılan belirsiz.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / aylikFaiz / description
      Previous value: -"Aylık akdi faiz oranı (%), ör. 3,5."New value: +"Aylık faiz (%), ör. 3,5."
    • changedInput schema / properties / konutFinansmani / description
      Previous value: -"Yalnız konut kredisinde: kredi mevzuattaki konut finansmanı niteliğinde mi (KKDF istisnası)? evet, hayir, belirsiz. Varsayılan belirsiz (istisna uygulanmaz)."New value: +"Konut kredisi: konut finansmanı niteliğinde mi (KKDF istisnası). Varsayılan belirsiz."
    • changedInput schema / properties / mevcutKonut / description
      Previous value: -"Yalnız konut kredisinde: kredi tarihinde kişinin üzerine kayıtlı konut veya konut hissesi var mı (BSMV istisnası yalnız \"yok\" ise)? yok, var, belirsiz. Varsayılan belirsiz."New value: +"Konut kredisi: üzerine kayıtlı konut/hisse var mı (yok ise BSMV istisnası). Varsayılan belirsiz."
    • changedInput schema / properties / tur / description
      Previous value: -"Kredi türü: ihtiyac-tasit, konut, ticari. Varsayılan ihtiyac-tasit."New value: +"Varsayılan ihtiyac-tasit."
    • changedInput schema / properties / tutar / description
      Previous value: -"Kredi tutarı (TL)."New value: +"TL."
    • changedInput schema / properties / vadeAy / description
      Previous value: -"Vade (ay)."New value: +"Ay."
  2. Changed2 schema fields changed
    • addedInput schema / properties / konutFinansmani
      Added value: +{
      +  "description": "Yalnız konut kredisinde: kredi mevzuattaki konut finansmanı niteliğinde mi (KKDF istisnası)? evet, hayir, belirsiz. Varsayılan belirsiz (istisna uygulanmaz).",
      +  "enum": [
      +    "evet",
      +    "hayir",
      +    "belirsiz"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / mevcutKonut
      Added value: +{
      +  "description": "Yalnız konut kredisinde: kredi tarihinde kişinin üzerine kayıtlı konut veya konut hissesi var mı (BSMV istisnası yalnız \"yok\" ise)? yok, var, belirsiz. Varsayılan belirsiz.",
      +  "enum": [
      +    "yok",
      +    "var",
      +    "belirsiz"
      +  ],
      +  "type": "string"
      +}
  3. First observed

TDQS

A3.6/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 the safety profile is fully covered. The description adds that tax output depends on the loan type (and implicitly on the housing-exemption parameters), which is genuine value, but it says nothing about rounding conventions, whether results are deterministic across types, or output shape beyond listing four quantities.

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 dense sentence that front-loads the action and then lists the outputs; no filler, no redundant restatement of the title.

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?

With no output schema, the description carries the burden of describing returns and does so by naming the four computed quantities. For a six-parameter calculator with fully documented schema this is nearly sufficient; only fiscal nuance (how exemptions change the tax line, rounding) is left implicit.

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 for tur, mevcutKonut and konutFinansmani, so every parameter is already documented, including defaults. The description adds only the loose link between loan type and tax calculation; it does not clarify how mevcutKonut or konutFinansmani alter the result, so the baseline 3 applies.

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 verb and resource (equal-installment loan calculation) and enumerates the computed outputs: installment, total payment, interest, and type-dependent BSMV/KKDF tax. It is clear what the tool produces, though it does not name the sibling kredi_erken_kapatma_hesapla to distinguish early-payoff scenarios from standard installment schedules.

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?

Usage is only implied — an agent can infer this is for standard amortizing loan schedules, but there is no explicit 'use this when…' statement, no mention that early payoff belongs to a different tool, and no note about required inputs like a positive rate or term limits already enforced by the schema.

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