Skip to main content
Glama

Emeklilik tarihi

emeklilik_tarihi_hesapla
Read-onlyIdempotent

"Ne zaman emekli olurum": giriş tarihi, prim günü, doğum tarihi ve cinsiyete göre prim, yaş ve sigortalılık şartlarını ve en erken tam emeklilik tarihini hesaplar (EYT ve kademeli yaş dahil). Kısmi emeklilik ve borçlanma hariç.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cinsiyet": "<cinsiyet>",
      "dogumTarihi": "<dogumTarihi>",
      "girisTarihi": "<girisTarihi>",
      "primGun": "<primGun>"
    },
    "name": "emeklilik_tarihi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
statuNo4a SSK, 4b Bağ-Kur, 4c memur. Varsayılan 4a.
primGunYesToplam prim (memurda hizmet) günü.
cinsiyetYes
dogumTarihiYesDoğum tarihi.
girisTarihiYesİlk sigorta giriş tarihi.
yillikPrimGunNoBundan sonra yıllık prim günü. Varsayılan 360.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedInput schema / properties / cinsiyet / description
      Removed value: -"Cinsiyet."
    • changedInput schema / properties / dogumTarihi / description
      Previous value: -"Doğum tarihi (YYYY-AA-GG)."New value: +"Doğum tarihi."
    • changedInput schema / properties / girisTarihi / description
      Previous value: -"İlk sigorta giriş tarihi (YYYY-AA-GG), e-Devlet hizmet dökümündeki ilk giriş."New value: +"İlk sigorta giriş tarihi."
    • changedInput schema / properties / primGun / description
      Previous value: -"Bugüne kadarki toplam prim (memurda hizmet) günü."New value: +"Toplam prim (memurda hizmet) günü."
    • changedInput schema / properties / statu / description
      Previous value: -"4a: işçi (SSK), 4b: Bağ-Kur (esnaf), 4c: memur. Varsayılan 4a."New value: +"4a SSK, 4b Bağ-Kur, 4c memur. Varsayılan 4a."
    • changedInput schema / properties / yillikPrimGun / description
      Previous value: -"Bundan sonra yılda ortalama kaç gün prim ödenecek. Varsayılan 360."New value: +"Bundan sonra yıllık prim günü. Varsayılan 360."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare a safe read-only, idempotent, closed-world calculation, so the bar is lower; the description still adds real scope context by disclosing which legal regimes are modeled (EYT, kademeli yaş) and which are out of scope (kısmi emeklilik, borçlanma). It does not specify the shape of the returned values (date plus which conditions are met), leaving a small gap for a calculator with no output schema.

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 tight sentences, front-loaded with the user-facing question 'Ne zaman emekli olurum' that helps routing, followed by scope and exclusions. No filler, though the parenthetical and trailing exclusions could be trimmed slightly without loss.

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?

For a six-parameter, side-effect-free calculator with rich annotations and no output schema, the description covers what is computed and what is out of scope. The remaining gap is that it does not hint at the returned breakdown (which conditions are satisfied) or the role of the future-accrual parameter, both of which an agent might want before calling.

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 83%, so the schema already documents the parameters; the description merely restates the four required inputs without adding format or interpretation detail. It says nothing about 'statu' (4a/4b/4c) or 'yillikPrimGun', the two parameters that materially change the projection, though both carry schema descriptions.

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 names a specific verb and resource ('en erken tam emeklilik tarihini hesaplar') and enumerates the inputs that drive the result (giriş tarihi, prim günü, doğum tarihi, cinsiyet). It also scopes the calculation (EYT ve kademeli yaş dahil) and excludes neighboring concerns, so it is distinguishable from siblings like memur_emekli_zammi_hesapla.

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?

It clearly states when this tool applies (full/standard retirement timing with EYT and graduated age rules) and explicitly excludes kısmi emeklilik and borçlanma, which is valuable when-not guidance. It does not name a sibling to use for those excluded cases, so it stops short of full alternative routing.

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