Skip to main content
Glama

Paranın bugünkü değeri

paranin_bugunku_degeri_hesapla
Read-onlyIdempotent

Geçmişteki bir TL tutarının bugünkü (ya da başka bir aydaki) karşılığını TÜİK TÜFE ile hesaplar: "2015'teki 1000 TL bugün kaç TL". Seri 2003'ten başlar; 2005 öncesi tutar eski TL sayılır. Asgari ücretin alım gücü değişimini de verir.

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": {
      "yil": "<yil>",
      "tutar": "<tutar>"
    },
    "name": "paranin_bugunku_degeri_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
ayNoBoşsa yıl ortalaması.
yilYesParanın yılı.
tutarYesTL (2005 öncesi eski TL).
hedefAyNoBoşsa son açıklanan ay (2026-10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / ay / description
      Previous value: -"Ay (1-12). Verilmezse yılın ortalaması."New value: +"Boşsa yıl ortalaması."
    • changedInput schema / properties / hedefAy / description
      Previous value: -"Karşılığın hesaplanacağı ay, YYYY-AA. Verilmezse son açıklanan ay (2026-10)."New value: +"Boşsa son açıklanan ay (2026-10)."
    • changedInput schema / properties / tutar / description
      Previous value: -"Tutar (TL; 2005 öncesi için eski TL)."New value: +"TL (2005 öncesi eski TL)."
    • changedInput schema / properties / yil / description
      Previous value: -"Paranın ait olduğu yıl."New value: +"Paranın yılı."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, and the description adds genuinely new context beyond them: the data source is TÜİK TÜFE, the series begins in 2003, and pre-2005 amounts are interpreted as old TL. It also discloses an extra output dimension (asgari ücret purchasing power change) that the agent would not otherwise expect.

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?

Three compact sentences that front-load the core computation and follow with scope limits. The example and the asgari ücret note both add value rather than repeat structured data.

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?

There is no output schema, so the description carries the burden of explaining return values; it says what is computed (present value plus minimum-wage purchasing power) but not the shape or units of the response. Input-domain caveats are well covered, so it is adequate but with a clear gap.

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 the schema already documents yil, ay, tutar and hedefAy including defaults. The description only reinforces the pre-2005 old-TL interpretation for tutar, adding little meaning beyond the schema; baseline 3 is appropriate.

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 (hesaplar), resource (geçmişteki bir TL tutarının bugünkü/başka bir aydaki karşılığı) and method (TÜİK TÜFE), with a concrete example. It does not name or distinguish itself from the close sibling enflasyon_etkisi_hesapla, so it stops short of a 5.

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 example '2015'teki 1000 TL bugün kaç TL' gives a clear usage scenario, and the 2003 series start plus the pre-2005 old-TL rule tell the agent when the input is valid. No explicit when-not-to-use or named alternative is given, which keeps it from a 5.

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