Skip to main content
Glama

Mevduat faizi

mevduat_faizi_hesapla
Read-onlyIdempotent

Vadeli mevduatın brüt faizini, güncel stopajını ve net getirisini 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": {
      "anapara": "<anapara>",
      "yillikFaiz": "<yillikFaiz>",
      "vadeGun": "<vadeGun>"
    },
    "name": "mevduat_faizi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
anaparaYesTL ya da döviz.
vadeGunYesGün, ör. 32.
hesapTuruNoVarsayılan tl.
yillikFaizYesYıllık brüt faiz (%).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / anapara / description
      Previous value: -"Yatırılan tutar (TL ya da döviz)."New value: +"TL ya da döviz."
    • changedInput schema / properties / hesapTuru / description
      Previous value: -"tl (TL mevduat/katılma) ya da doviz. Varsayılan tl."New value: +"Varsayılan tl."
    • changedInput schema / properties / vadeGun / description
      Previous value: -"Vade, gün (ör. 32)."New value: +"Gün, ör. 32."
    • changedInput schema / properties / yillikFaiz / description
      Previous value: -"Yıllık brüt faiz oranı (%)."New value: +"Yıllık brüt faiz (%)."
  2. First observed

TDQS

B3.2/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. The description adds real behavioral context by revealing that the computation applies a "güncel" (current) withholding rate and yields both gross and net figures, but it says nothing about compounding conventions, day-count basis, or which stopaj bracket applies for a given maturity and hesapTuru.

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?

A single well-formed sentence with no filler, and the resource is front-loaded before the list of computed outputs. It is efficient, though the brevity leaves room that could have been spent on assumptions rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter financial calculator with full schema coverage, rich annotations, and no output schema, the description correctly states what is returned (gross, stopaj, net). The gap is that Turkish withholding tax depends on both maturity and currency type, yet the description never says how vadeGun and hesapTuru affect the stopaj, nor what assumptions the calculation makes.

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% – every parameter, including the hesapTuru enum with its "Varsayılan tl" default, is documented in the schema. The description contributes no additional parameter meaning beyond what the schema states, 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?

The description names a specific verb ("hesaplar") and a specific resource ("Vadeli mevduatın brüt faizi"), and it enumerates the three outputs produced: gross interest, current withholding tax, and net return. That is enough to separate it from sibling calculators like kredi_hesapla or kira_artis_hesapla, though it never explicitly contrasts itself with any of them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no when-to-use guidance, no prerequisites, and no alternatives or exclusions. An agent must infer from the tool name and the Turkish term "vadeli mevduat" alone that this applies to time deposits rather than other savings or loan products.

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