Skip to main content
Glama
denizcakiroglu322

evds-mcp-server

Dış Ticaret (İhracat / İthalat / Denge)

get_trade_balance
Read-onlyIdempotent

Retrieve Turkey's foreign trade data: exports, imports, or trade balance (in thousand USD) for a specified period. Use to answer questions about monthly trade figures or deficits.

Instructions

Türkiye dış ticareti: ihracat, ithalat veya dış ticaret dengesi (aylık, bin USD).

Ne zaman kullanılır:

  • "İhracat/ithalat X ayında ne kadardı", "dış ticaret açığı son dönemde nasıl" sorularında.

  • flow='balance' → ihracat − ithalat (negatif = açık).

Parametreler:

  • flow: 'export' | 'import' | 'balance'

  • period: { start, end }

Dönüş: ortak şema — unit 'bin USD', basis 'düzey' (balance için 'düzey (ihracat − ithalat)'). Seri: Genel Ticaret Sistemi, ISIC Rev.4 Toplam (ihracat TP.IHRISICREV4.TT / ithalat TP.ITHISICREV4.TT).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flowYes'export' = ihracat, 'import' = ithalat, 'balance' = denge (ihracat − ithalat).
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.
Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint true, consistent with a query tool. The description adds context about the data computation (balance = export - import) and return format, going beyond 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?

Well-structured with clear sections; each sentence adds necessary information. Slightly verbose but justified given the multilingual context and detail.

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?

Tool is moderately complex with nested period parameter and return schema. Description covers purpose, when to use, parameter details, and return format. Output schema exists, so return values need not be fully described here.

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% description coverage, so baseline is 3. The description adds value by explaining the 'flow' parameter with examples and detailing the specific series codes used.

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?

The description clearly states the tool retrieves Turkey's foreign trade data (export, import, balance) in monthly thousand USD. It distinguishes itself from sibling tools like get_growth or get_inflation, which focus on other economic indicators.

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?

Includes a 'Ne zaman kullanılır' section with example questions, guiding when to use the tool. It does not explicitly list alternatives, but the sibling tools are sufficiently different in purpose.

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