Skip to main content
Glama

Döviz kurları ve ekonomik göstergeler

doviz_ve_gostergeler
Read-onlyIdempotent

TCMB EVDS verisiyle güncel dolar, euro, sterlin, altın, politika faizi, enflasyon, konut fiyat endeksi, rezervler ve piyasa katılımcıları anketi. Varsayılan: dolar, euro, altın, faiz, enflasyon.

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_ve_gostergeler"
  }
}

Input Schema

NameRequiredDescriptionDefault
gostergelerNoör. ["dolar", "euro", "altın", "faiz", "enflasyon", "konut", "rezerv", "beklenti"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine context beyond that: the upstream source (TCMB EVDS) and the default indicator set applied when the parameter is omitted. It stops short of describing what happens on an unrecognized indicator name or whether all indicators are returned in one payload.

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 sentences, no filler, with the data source and scope front-loaded ahead of the default-behavior clause. The density is high, though the enumerated Turkish phrases are not aligned with the accepted parameter keys, so the compactness partly comes at the cost of operability.

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

Completeness3/5

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

For a one-optional-parameter read-only tool with full schema coverage and strong annotations, the description covers purpose, source, and default behavior adequately. Because no output schema exists, however, nothing explains the shape of the returned data (per-indicator values, date fields, units, error behavior for bad keys), which is the remaining gap an agent would want closed.

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 the single optional parameter already carries an example array, so the schema does most of the work. The description's enumeration does add one value not in the schema example (sterlin) and clarifies the default set, but it creates mapping ambiguity by naming concepts as "konut fiyat endeksi" and "piyasa katılımcıları anketi" while the schema uses the short keys "konut" and "beklenti" — the description never states which literal string to pass.

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 concrete resource set (dolar, euro, sterlin, altın, faiz, enflasyon, konut fiyat endeksi, rezervler, beklenti anketi) served from TCMB EVDS data, which makes the tool's scope unambiguous. No sibling tool (hukuk_terimi, son_yazilar, tarif_bul, yazi_ara, yazi_ozeti) overlaps with this domain, so explicit sibling differentiation is unnecessary and its absence costs little.

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: the reader infers this is the tool for financial/economic figures. The one piece of real guidance is "Varsayılan: dolar, euro, altın, faiz, enflasyon," which tells the agent what happens if it omits the parameter. There is no statement of when NOT to use it, and no mention of how to handle an unsupported indicator name.

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