Skip to main content
Glama

Kıdem ve ihbar tazminatı

kidem_ihbar_tazminati_hesapla
Read-onlyIdempotent

Kıdem (1475 s. Kanun md. 14) ve ihbar (4857 s. Kanun md. 17) tazminatını brüt hesaplar. Yol, yemek, ikramiye eklenebilir; ayrılış tarihindeki dönemin kıdem tavanı uygulanır.

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": {
      "brutMaas": "<brutMaas>",
      "iseBaslama": "<iseBaslama>"
    },
    "name": "kidem_ihbar_tazminati_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
yolNoAylık yol yardımı (TL).
digerNoDiğer sürekli aylık menfaatler (TL).
yemekNoAylık yemek yardımı (TL).
brutMaasYesAylık çıplak brüt maaş (TL).
ikramiyeNoİkramiyenin aya düşen payı (TL).
iseBaslamaYesİşe başlama tarihi.
istenAyrilisNoİşten ayrılış tarihi. Boşsa bugün.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / diger / description
      Previous value: -"Diğer süreklilik arz eden aylık menfaatler (TL). İsteğe bağlı."New value: +"Diğer sürekli aylık menfaatler (TL)."
    • changedInput schema / properties / ikramiye / description
      Previous value: -"İkramiyenin aya düşen payı (TL). İsteğe bağlı."New value: +"İkramiyenin aya düşen payı (TL)."
    • changedInput schema / properties / iseBaslama / description
      Previous value: -"İşe başlama tarihi, YYYY-AA-GG."New value: +"İşe başlama tarihi."
    • changedInput schema / properties / istenAyrilis / description
      Previous value: -"İşten ayrılış tarihi, YYYY-AA-GG. Boş bırakılırsa bugün (Türkiye)."New value: +"İşten ayrılış tarihi. Boşsa bugün."
    • changedInput schema / properties / yemek / description
      Previous value: -"Aylık yemek yardımı (TL). İsteğe bağlı."New value: +"Aylık yemek yardımı (TL)."
    • changedInput schema / properties / yol / description
      Previous value: -"Aylık yol yardımı (TL). İsteğe bağlı."New value: +"Aylık yol yardımı (TL)."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds substantive behavior: results are gross ("brüt hesaplar") rather than net, the severance cap of the departure-period is applied, and side benefits may be folded in. What it omits is whether kıdem and ihbar come back as separate line items and how the notice period interacts with tenure.

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?

Two compact sentences with no padding, and the core scope plus statutory basis is front-loaded before the optional add-ons and the cap rule. Every clause carries information an agent cannot get from the schema alone.

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 seven-parameter calculation tool with no output schema, the description says nothing about the shape of the result, so an agent cannot know whether it receives a combined total, separate kıdem/ihbar figures, or the cap amount actually applied. Safety behavior is fully covered by annotations, so the residual gap is limited to output expectations rather than invocation risk.

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%, so every one of the seven parameters is already self-documenting, which sets the baseline at 3. The description's note that yol, yemek and ikramiye can be added maps onto the optional fields but adds no format or rate-of-inclusion detail beyond the schema, and it never mentions the istenAyrilis default-to-today rule that the schema states.

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?

States a specific verb (hesaplar) and precise resources (kıdem ve ihbar tazminatı) with statutory citations (1475 s. K. md. 14, 4857 s. K. md. 17), so the domain is unmistakable. It does not differentiate itself from the plausible sibling isten_ayrilma_alacaklari_hesapla, which appears to cover overlapping end-of-employment payouts, leaving an ambiguity an agent must resolve on its own.

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 by the subject matter: an agent can infer this applies when a worker's severance and notice entitlements must be computed. There is no explicit when-to-use, no exclusion, and no pointer to the sibling that also deals with exit receivables, so routing between them is left to inference.

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