Skip to main content
Glama

Döviz çevirici

doviz_cevir
Read-onlyIdempotent

TL ile döviz arasında TCMB'nin son günlük kuruyla çeviri yapar; bülten tarihi cevaptadır. Kur elle de verilebilir.

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>",
      "doviz": "<doviz>"
    },
    "name": "doviz_cevir"
  }
}

Input Schema

NameRequiredDescriptionDefault
kurNo1 birim kaç TL; TCMB kuru yerine.
yonNotl-doviz: tutar TL. Varsayılan tl-doviz.
dovizYesÖr. USD.
tutarYesÇevrilecek tutar.
kurTuruNodovizSatis: döviz alırken; dovizAlis: bozdururken; efektif: nakit. Varsayılan dovizSatis.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / doviz / description
      Previous value: -"Döviz kodu, ör. USD, EUR, GBP."New value: +"Ör. USD."
    • changedInput schema / properties / kur / description
      Previous value: -"İsteğe bağlı: 1 birim döviz kaç TL. Verilirse TCMB kuru yerine bu kullanılır."New value: +"1 birim kaç TL; TCMB kuru yerine."
    • changedInput schema / properties / kurTuru / description
      Previous value: -"dovizSatis (hesaptan döviz alırken), dovizAlis (bozdururken), efektifSatis / efektifAlis (nakit). Varsayılan dovizSatis."New value: +"dovizSatis: döviz alırken; dovizAlis: bozdururken; efektif: nakit. Varsayılan dovizSatis."
    • changedInput schema / properties / yon / description
      Previous value: -"tl-doviz: tutar TL'dir, dövize çevrilir. doviz-tl: tutar dövizdir, TL'ye çevrilir. Varsayılan tl-doviz."New value: +"tl-doviz: tutar TL. Varsayılan tl-doviz."
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral facts: the conversion uses the TCMB latest daily rate, the bulletin date is returned in the response, and the rate can be supplied manually. It does not discuss rate staleness handling or rounding, but the freshness/source disclosure is substantive value beyond the annotations.

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 short, front-loaded sentences that spend no words on filler; the core purpose and the data source come first. The second clause about manual rates is brief and relevant, though it could be merged more tightly with the first sentence.

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 five parameters, three enums, and no output schema, the definition covers the essentials: what is converted, the rate source, the manual override, and the fact that a bulletin date is returned (compensating partly for the missing output schema). It does not mention rounding or what happens if the bulletin has no rate for a currency, which are minor residual gaps.

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%, including enum explanations for yon, kurTuru and doviz, so the schema carries the parameter burden and the baseline is 3. The description adds only the manual-rate override note, which the 'kur' schema entry already states, so it contributes little meaning beyond the structured data.

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 states a specific verb and resource ('TL ile döviz arasında ... çeviri yapar') and names the rate source (TCMB son günlük kuru), which makes it clearly a conversion tool rather than the sibling rate-fetch tool. It does not explicitly name doviz_kuru_getir as the alternative, so it falls short of full sibling differentiation.

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 implied rather than stated: the agent can infer this is for converting an amount, and 'Kur elle de verilebilir' signals an override path. There is no explicit when-to-use versus when-to-fetch-the-rate guidance and no prerequisites or exclusions, so the agent must infer the boundary with doviz_kuru_getir.

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