Skip to main content
Glama
TurkActuary MCP

TurkActuary MCP

by afsharid

is_goremezlik

Read-onlyIdempotent

Calculates permanent and temporary disability compensation under Turkish Court of Cassation actuarial practice, returning period tables, assumptions, and decision IDs.

Instructions

Sürekli/geçici iş göremezlik tazminatı (Yargıtay uygulaması: TRH 2010 bakiye ömür kaza tarihindeki yaşa göre, bilinen dönem iskontosuz, bilinmeyen dönem %10 artış/%10 iskonto progresif rant, 60 yaşa kadar aktif sonra pasif; indirim sırası kusur → hatır → müterafik → SGK → önceki ödemeler). Dönem tablosu, varsayımlar ve karar kimlikleri döner. Bilirkişi raporu yerine geçmez.

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>",
      "dogum_tarihi": "<dogum_tarihi>",
      "kaza_tarihi": "<kaza_tarihi>",
      "hesap_tarihi": "<hesap_tarihi>",
      "surekli_maluliyet_orani": "<surekli_maluliyet_orani>",
      "gelir_donemleri": "<gelir_donemleri>",
      "son_aylik_net": "<son_aylik_net>"
    },
    "name": "is_goremezlik"
  }
}

Input Schema

NameRequiredDescriptionDefault
cinsiyetYes
artis_oraniNoProgresif rant artış oranı; varsayılan 0.10
kaza_tarihiYesYYYY-AA-GG
dogum_tarihiYesYYYY-AA-GG
hesap_tarihiYesYYYY-AA-GG
iskonto_oraniNoProgresif rant iskonto oranı; varsayılan 0.10
son_aylik_netYesBilinmeyen dönem (aktif) için bilinen son net aylık gelir
hatir_indirimiNoHatır taşıması indirimi; somut olaya göre (ör. 0.10–0.20)
bakiye_omur_yilNoElle bakiye ömür (ör. davacı PMF 1931 talep ettiyse); verilmezse TRH 2010
gelir_donemleriYesBilinen dönem net aylık gelirleri; kaza/ölüm tarihinden hesap tarihine boşluksuz.
pasif_aylik_netNoPasif dönem net aylık geliri; verilmezse hesap tarihindeki net asgari ücret (tablodan; hesap tarihi 2022 öncesiyse zorunlu)
sgk_mahsup_oraniNoPSD'nin düşülecek oranı; varsayılan 1 (5510 m.21/4 iş kazasında 0.5)
sorumlu_kusur_oraniNoSorumlu tarafın (sigortalının) kusur oranı; varsayılan 1
aktif_donem_sonu_yasiNoVarsayılan 60
onceki_odemeler_guncelNoGüncellenmiş önceki ödemeler
surekli_maluliyet_oraniYes0–1 arası oran (0.10 = %10)
gecici_is_goremezlik_gunNoKazadan itibaren %100 iş göremezlik günü
kaza_tarihinde_calisiyorNo18 yaş altında geçici iş göremezlik için gerekli
muterafik_kusur_indirimiNoMüterafik kusur indirimi (ör. kask/kemer: 0.20)
sgk_pesin_sermaye_degeriNoYalnız rücuya tabi SGK gelirinin ilk peşin sermaye değeri

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description's job is to add domain behavior — which it does: TRH 2010 table with age at accident date, undiscounted known period, 10% increase/discount progressive annuity for the unknown period, active-to-60 then passive, and an explicit deduction order (kusur → hatır → müterafik → SGK → önceki ödemeler). It also discloses the return payload (period table, assumptions, decision IDs) and a legal-scope disclaimer, which are genuine additions beyond the 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?

Purpose is front-loaded in the first clause, then the methodology is packed into a single parenthetical block that earns its length by encoding real assumptions and ordering rules. The two closing sentences (return contents, non-substitution disclaimer) are short and high-value. The dense legal terminology is appropriate for the domain but makes the middle block harder to scan.

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 20-parameter, no-output-schema actuarial tool this is nearly complete: it states the methodology, the default assumptions, the deduction sequence, and what is returned. What is missing are cross-field preconditions (e.g., date ordering, the schema's 'boşluksuz' income-period continuity rule, the mandatory pasif_aylik_net for pre-2022 hesap_tarihi) stated as call-level constraints rather than relying solely on the schema.

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 coverage is 95%, so the schema already carries most parameter meaning and a baseline of 3 would be defensible. The description nonetheless explains the reasoning behind key defaults — the 10%/10% progressive annuity rates, the 60-year active cutoff, and the default TRH 2010 balance-of-life that bakiye_omur_yil overrides — which helps the agent understand rather than just pass these values.

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 specific legal-financial computation (sürekli/geçici iş göremezlik tazminatı) and enumerates the actuarial method behind it, so an agent knows exactly what is being calculated. It never names the closest sibling (destekten_yoksun_kalma, the death/loss-of-support counterpart), so differentiation is left to the agent's own inference.

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 computes disability compensation under Yargıtay practice, and the closing sentence 'Bilirkişi raporu yerine geçmez' scopes it as a calculation aid rather than an authoritative report. There is no explicit statement of when to pick this over destekten_yoksun_kalma or annuity, and no prerequisites for calling it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.