Skip to main content
Glama
denizcakiroglu322

evds-mcp-server

by denizcakiroglu322
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Döviz Kuru (TCMB)

get_fx
Read-onlyIdempotent

Retrieves daily TCMB buying or selling rates for major currencies against the Turkish lira for a specified date range.

Instructions

TCMB'nin gösterge niteliğindeki günlük döviz alış/satış kurlarını döndürür (1 birim yabancı para = X TL).

Ne zaman kullanılır:

  • "Dolar/Euro kuru bugün/şu tarihte neydi", "son 1 yılda dolar nasıl değişti" gibi sorularda.

  • Kur SEVİYESİ (TL) gerekir; yüzde değişim gerekiyorsa observations'tan hesaplayın ya da compare_indicators kullanın.

Parametreler:

  • pair: USD | EUR | GBP | CHF | CAD | AUD | SAR | DKK | SEK | NOK

  • side: 'alis' | 'satis' (vars. 'satis')

  • period: { start, end } (YYYY | YYYY-MM | YYYY-MM-DD)

Dönüş: ortak şema — series, label, unit ("TL (1 karşılığı)"), basis ("nominal"), observations[{date,value}], source, fetchedAt. Notlar: Hafta sonu/tatil günlerinde değer null olabilir. Veri yoksa uydurmaz; not alanında belirtir.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairYesCurrency against TRY. One of: USD, EUR, GBP, CHF, CAD, AUD, SAR, DKK, SEK, NOK.
sideNo'alis' = TCMB buying rate, 'satis' = TCMB selling rate (default).satis
periodYesInclusive date range to query.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteNoMethodology, caveats, or verification warnings, when relevant.
unitYesUnit of the values, e.g. '%', 'TL', 'endeks (2003=100)'.
basisYesWhat the numbers represent: 'nominal' | 'reel' | 'düzey' | 'yıllık % değişim' | ...
labelYesHuman-readable Turkish name of the series.
seriesYesEVDS series code that produced these observations (e.g. 'TP.DK.USD.A.YTL').
sourceYesAlways 'TCMB EVDS'.
fetchedAtYesISO-8601 timestamp of when the data was fetched.
observationsYesThe time series, oldest to newest.

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. Description adds valuable context: weekend/holiday null values, data absence handling via note field, and return structure summary. No contradictions.

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?

Well-structured with clear sections (purpose, when to use, parameters, return). Front-loaded key info. No unnecessary words; every sentence serves a purpose.

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

Completeness5/5

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

Given 3 parameters (including nested period), output schema exists, and context signals high complexity. Covers return format, unit, basis, and edge cases (holidays null). Completely equips an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with full descriptions for all parameters. Description goes beyond by explaining side meanings (alis/satis) and providing usage examples in context. Adds value without redundancy.

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?

Explicitly states it returns daily FX rates from TCMB, with resource (currency pairs) and verb (döndürür). Distinguishes from sibling compare_indicators by specifying it provides rate levels (TL) vs percentage changes.

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

Usage Guidelines5/5

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

Clearly states when to use (rate levels for currencies) and when not (percentage changes should use compare_indicators or compute from observations). Provides explicit alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/denizcakiroglu322/evds-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server