Skip to main content
Glama

Güncel döviz kuru (TCMB)

doviz_kuru_getir
Read-onlyIdempotent

"Dolar kaç TL" gibi sorular için TCMB'nin son günlük bültenindeki döviz ve efektif alış/satış kurlarını, bülten tarihi ve kaynağıyla verir. Tutar çevirmez.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doviz_kuru_getir"
  }
}

Input Schema

NameRequiredDescriptionDefault
dovizlerNoÖr. ["USD"]. Boşsa USD, EUR, GBP.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / dovizler / description
      Previous value: -"Üç harfli döviz kodları (ör. USD, EUR, CHF). Boşsa USD, EUR ve GBP döner."New value: +"Ör. [\"USD\"]. Boşsa USD, EUR, GBP."
  2. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds real context beyond that: results come from the latest daily bulletin (data freshness limit) and include bulletin date and source, and amounts are not converted. Missing is any note on what happens with unsupported codes or how rates are quoted per unit.

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 sentences, front-loaded with the user question it answers, then the data provenance and the scope limit. No filler, though the negation sentence could be phrased to also name the conversion alternative.

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 rich annotations, a fully described single parameter, and no output schema, the description covers what is returned (buy/sell and effective rates plus bulletin date and source) and its limit. It could add how rates are quoted (per 1 unit) and behavior for unknown currency codes, but nothing critical is missing for correct invocation.

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 coverage is 100% and the single optional parameter already documents the example (["USD"]) and the default (USD, EUR, GBP), so the description need not repeat it. The description adds no syntax or semantic detail about currency codes or the 30-item cap, leaving it at the baseline.

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?

Description uses a concrete verb and resource ('döviz ve efektif alış/satış kurlarını ... verir') sourced from a named authority (TCMB) and bulletin. The clause 'Tutar çevirmez' effectively separates it from the conversion sibling doviz_cevir, so an agent can pick correctly without reading schemas.

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?

Gives a concrete trigger case ('"Dolar kaç TL" gibi sorular için') and rules out conversion work, which implicitly routes those requests elsewhere. It stops short of naming the alternative tool or stating exclusions like historical rate queries, so not a full 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