Skip to main content
Glama

TCMB döviz kurları

finans_get_exchange_rates

Retrieve official Central Bank of Türkiye exchange rates for today or a past date, including forex and banknote buying/selling rates in TRY.

Instructions

Official Central Bank of Türkiye (TCMB) exchange rates (döviz kuru, dolar, euro, sterlin) for today or a past date. Returns forex and banknote buying/selling rates in TRY.

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": "finans_get_exchange_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
tarihNoGeçmiş tarih (YYYY-MM-DD). Boşsa bugünün bülteni.
kodlarNoYalnız bu döviz kodları, ör. ["USD","EUR"]. Boşsa hepsi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full load. It does disclose the return shape at a high level (forex and banknote buying/selling rates in TRY), which is useful behavioral context beyond the schema. It omits operational facts an agent would want: behavior on weekends/holidays when TCMB publishes no bulletin, historical range limits, and whether the call is purely read-only.

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?

Two sentences, front-loaded with the authoritative source and scope, with return content second. The parenthetical Turkish synonyms are not padding; they are the phrases an agent would match against a Turkish user request.

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 two optional parameters, no output schema, and no annotations, the definition should mostly explain what comes back and when it applies. It does the former well and the latter adequately, but the absence of any note on non-publication days or historical coverage leaves a real gap for a date-parameterized financial lookup.

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%, and both parameters (tarih as YYYY-MM-DD, kodlar as a filter array) are already documented in the schema. The description adds nothing about parameter behavior beyond the schema, but the baseline of 3 applies when the schema does the heavy lifting.

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 resource and authority: official TCMB exchange rates, today or a past date, returning forex and banknote buy/sell rates in TRY. The Turkish keyword synonyms (döviz kuru, dolar, euro, sterlin) make the tool's domain unmistakable against the crypto and gold price siblings. It stops short of naming a sibling explicitly, so it is clear but not fully differentiated by contrast.

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: fetch current or historical TCMB rates, with scope given as 'today or a past date'. There is no guidance on when to prefer this over finans_get_crypto_prices or finans_get_gold_prices, and no statement of how far back historical lookups are supported.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.