Skip to main content
Glama

Güncel resmî oran ve tutarlar

guncel_veri_getir
Read-onlyIdempotent

Türkiye'deki güncel resmî oran, tavan ve tutarları (asgari ücret, vergi dilimleri, SGK, kıdem tavanı, KDV, stopaj vb.) dönem, geçerlilik bitişi ve yasal dayanakla verir; son değişiklikler de döner.

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

Input Schema

NameRequiredDescriptionDefault
anahtarNoBoşsa kayıt listesi.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / anahtar / description
      Previous value: -"İstenen kaydın anahtarı. Boş bırakılırsa bütün kayıtların anahtarı, başlığı ve dönemi listelenir."New value: +"Boşsa kayıt listesi."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description still adds value by stating that each answer carries dönem, geçerlilik bitişi and yasal dayanak, and that recent changes are returned too — useful for an agent reasoning about freshness. It stops short of describing the shape of those returns or of an empty-key listing behaviour.

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?

One front-loaded sentence naming the resource first, then the examples, then the payload attributes. The long parenthetical is dense but earns its place as a matching aid for the enum keys.

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?

No output schema exists, and the description compensates by naming the three metadata fields returned with every value plus the recent-changes note. What remains thin — return format details and the empty-parameter listing path — is minor for a one-optional-parameter read-only 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 coverage is 100% and the single optional enum parameter is fully enumerated in the schema, including the "Boşsa kayıt listesi" note. The description adds no meaning beyond that — it never mentions the anahtar parameter or explain how the parenthetical examples map onto enum keys.

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?

Specific verb+resource: "güncel resmî oran, tavan ve tutarları ... verir", reinforced by a concrete parenthetical list (asgari ücret, vergi dilimleri, SGK, kıdem tavanı, KDV, stopaj). It does not, however, name a sibling or state how it differs from the many *_hesapla tools alongside it.

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 tool supplies authoritative reference values, which an agent can infer it should call before or instead of computing. There is no explicit when-to-use, when-not-to-use, or routing to alternatives such as kdv_hesapla or kidem_ihbar_tazminati_hesapla, which presumably consume these values.

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