Skip to main content
Glama

Güncel enflasyon oranı (TÜFE, TÜİK)

enflasyon_orani_getir
Read-onlyIdempotent

"Enflasyon kaç oldu", "kira artış oranı kaç" gibi sorular için TÜİK'in son aylık ve yıllık TÜFE değişimini ve kira tavanı olan on iki aylık ortalamayı dönem, kaynak ve sonraki bülten tarihiyle verir.

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

Input Schema

NameRequiredDescriptionDefault
gecmisAyNoGeçmiş ay sayısı. Varsayılan 6.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / gecmisAy / description
      Previous value: -"Kaç aylık geçmiş değer dönsün. Varsayılan 6."New value: +"Geçmiş ay sayısı. Varsayılan 6."
  2. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, closed-world operation, so the safety profile is covered. The description usefully adds what payload comes back (period, source, next bulletin date), giving the agent freshness context. However, it says nothing about caching, data lag, or fallback behavior if TÜİK data is unavailable, which is the main residual gap for a live-statistics tool.

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?

A single sentence that front-loads the triggering user questions and then lists the returned data points in a compact clause. No filler, no repetition of the title or name, and the most decision-relevant information comes first.

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 no output schema, the description carries the burden of describing returns and does so: monthly and annual change, twelve-month average, period, source, next bulletin date. What it omits is the effect of the gecmisAy parameter on the result set, which leaves a small gap for a tool whose main complexity is its data payload.

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 gecmisAy is fully documented in the schema with its default and 1-24 bounds. The description never mentions the parameter, so it adds nothing beyond the schema, but with complete schema coverage the baseline of 3 is appropriate.

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?

Names a specific verb and resource: it returns TÜİK's latest monthly and annual CPI change plus the twelve-month average used as the rent ceiling, along with period, source, and next release date. The purpose is unambiguous, but it does not explicitly distinguish itself from calculation siblings like kira_artis_hesapla or enflasyon_etkisi_hesapla, which deal with the same domain.

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?

Opens with concrete example questions ('Enflasyon kaç oldu', 'kira artış oranı kaç') that clearly signal when to reach for this tool. There are no explicit exclusions telling the agent when a sibling calculator is the better choice, so it stops short of full routing guidance.

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