Skip to main content
Glama

Yıllık izin

yillik_izin_hesapla
Read-onlyIdempotent

Yıllık ücretli izin (4857 s. Kanun md. 53): kıdem ve yaşa göre hak, toplam ve kalan gün, sonraki iznin doğacağı tarih.

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": {
      "iseGiris": "<iseGiris>"
    },
    "name": "yillik_izin_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
yasNoYaş (18 altı ve 50 üstü en az 20 gün).
iseGirisYesİşe giriş tarihi.
yeraltiIsiNoVarsayılan false.
hesapTarihiNoBoşsa bugün.
kullanilanGunNoKullanılan izin günü. Varsayılan 0.
oncekiHizmetYiliNoAynı işverende önceki hizmet (yıl). Varsayılan 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / hesapTarihi / description
      Previous value: -"Hangi tarih itibarıyla, YYYY-AA-GG. Boşsa bugün."New value: +"Boşsa bugün."
    • changedInput schema / properties / iseGiris / description
      Previous value: -"İşe giriş tarihi, YYYY-AA-GG."New value: +"İşe giriş tarihi."
    • changedInput schema / properties / kullanilanGun / description
      Previous value: -"Bugüne kadar kullanılan izin günü. Varsayılan 0."New value: +"Kullanılan izin günü. Varsayılan 0."
    • changedInput schema / properties / oncekiHizmetYili / description
      Previous value: -"Aynı işverenin başka işyerlerindeki önceki hizmet, yıl. Varsayılan 0."New value: +"Aynı işverende önceki hizmet (yıl). Varsayılan 0."
    • changedInput schema / properties / yas / description
      Previous value: -"Çalışanın yaşı (18 yaş altı ve 50 yaş üstü için en az 20 gün kuralı)."New value: +"Yaş (18 altı ve 50 üstü en az 20 gün)."
    • changedInput schema / properties / yeraltiIsi / description
      Previous value: -"Yer altı işlerinde mi çalışıyor? Varsayılan false."New value: +"Varsayılan false."
  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 declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. Beyond that the description adds real value by disclosing the return content (total days, remaining days, next accrual date) and grounding the calculation in the statutory article, which matters because no output schema exists.

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?

A single dense sentence that front-loads the legal basis and then lists the computed outputs. The statutory citation costs a few words but anchors the calculation to a known rule; nothing is redundant or padded.

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, annotation-backed calculation tool with no output schema, the description covers the legal basis and the shape of the result well. Minor gaps remain: it does not explain the effect of yeraltiIsi (underground work lowering the service threshold) or how hesapTarihi and kullanilanGun interact with the result, but the schema descriptions cover those defaults.

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% — every parameter including yas, iseGiris, yeraltiIsi, hesapTarihi, kullanilanGun and oncekiHizmetYili carries its own description and defaults. The description only echoes the two drivers ('kıdem ve yaşa göre') without adding format or edge-case detail beyond the schema, so the baseline 3 applies.

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 resource (yıllık ücretli izin under Law 4857 Art. 53) and enumerates exactly what is computed: entitlement by seniority and age, total and remaining days, and the next accrual date. That is enough to separate it from siblings like kidem_ihbar_tazminati_hesapla or fazla_mesai_hesapla, though it never explicitly names an alternative or states the verb 'calculate'.

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 domain: an agent can infer this is the tool for annual leave entitlement questions. There is no explicit when-to-use statement, no mention of when another tool (e.g. severance or overtime) is the right call, and no prerequisites or exclusions.

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