Skip to main content
Glama

Fazla mesai

fazla_mesai_hesapla
Read-onlyIdempotent

Bir haftanın fazla mesai ücretini (4857 s. Kanun md. 41), genel ve hafta tatili çalışmasını ve yıllık 270 saat sınırını brüt hesaplar. haftalikCalisilanSaat o haftanın toplam saatidir (ör. 52), yalnız fazla mesai değil.

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>",
      "haftalikCalisilanSaat": "<haftalikCalisilanSaat>"
    },
    "name": "fazla_mesai_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
brutMaasYesAylık brüt maaş (TL).
yeraltiIsiNoYer altı maden işi (37,5 saat). Varsayılan false.
genelTatilGunuNoÇalışılan resmî tatil/bayram günü. Varsayılan 0.
haftaTatiliGunuNoÇalışılan hafta tatili günü. Varsayılan 0.
ucreteDahilMaddesiNoSözleşmede "fazla mesai ücrete dahil" maddesi. Varsayılan false.
sozlesmeHaftalikSaatNoSözleşmedeki haftalık saat. Varsayılan 45.
haftalikCalisilanSaatYesO haftaki TOPLAM saat, normal saatler dahil (0-168).
yilIcindekiFazlaMesaiNoBu yıl önceden yapılan fazla mesai saati. Varsayılan 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • changedInput schema / properties / genelTatilGunu / description
      Previous value: -"Çalışılan genel tatil (bayram, resmî tatil) günü (0-31). Varsayılan 0."New value: +"Çalışılan resmî tatil/bayram günü. Varsayılan 0."
    • changedInput schema / properties / haftaTatiliGunu / description
      Previous value: -"Çalışılan hafta tatili günü (0-31). Varsayılan 0."New value: +"Çalışılan hafta tatili günü. Varsayılan 0."
    • changedInput schema / properties / haftalikCalisilanSaat / description
      Previous value: -"O hafta fiilen çalışılan TOPLAM saat (0-168; ör. 52). Fazla mesai saati değil, normal saatler dahil toplam."New value: +"O haftaki TOPLAM saat, normal saatler dahil (0-168)."
    • changedInput schema / properties / sozlesmeHaftalikSaat / description
      Previous value: -"Sözleşmedeki haftalık çalışma süresi (1-45). Varsayılan 45."New value: +"Sözleşmedeki haftalık saat. Varsayılan 45."
    • changedInput schema / properties / ucreteDahilMaddesi / description
      Previous value: -"Sözleşmede \"fazla mesai ücrete dahildir\" maddesi var mı? Varsayılan false."New value: +"Sözleşmede \"fazla mesai ücrete dahil\" maddesi. Varsayılan false."
    • changedInput schema / properties / yeraltiIsi / description
      Previous value: -"Yer altı maden işi mi (haftalık yasal süre 37,5 saat)? Varsayılan false."New value: +"Yer altı maden işi (37,5 saat). Varsayılan false."
    • changedInput schema / properties / yilIcindekiFazlaMesai / description
      Previous value: -"Bu yıl daha önce yapılan fazla mesai saati. Varsayılan 0."New value: +"Bu yıl önceden yapılan fazla mesai saati. Varsayılan 0."
  2. Changed3 schema fields changed
    • changedInput schema / properties / genelTatilGunu / description
      Previous value: -"Çalışılan genel tatil (bayram, resmî tatil) günü. Varsayılan 0."New value: +"Çalışılan genel tatil (bayram, resmî tatil) günü (0-31). Varsayılan 0."
    • changedInput schema / properties / haftaTatiliGunu / description
      Previous value: -"Çalışılan hafta tatili günü. Varsayılan 0."New value: +"Çalışılan hafta tatili günü (0-31). Varsayılan 0."
    • changedInput schema / properties / haftalikCalisilanSaat / description
      Previous value: -"O hafta fiilen çalışılan toplam saat."New value: +"O hafta fiilen çalışılan TOPLAM saat (0-168; ör. 52). Fazla mesai saati değil, normal saatler dahil toplam."
  3. First observed

TDQS

A4.2/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. The description adds real behavioral substance beyond that: results are gross, the calculation includes holiday and rest-day work as well as the statutory 270-hour ceiling, which an agent could not infer from annotations alone.

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 sentences, both front-loaded and purposeful: first the scope and legal basis, then the one parameter caveat most likely to cause an error. No filler or restatement of the tool name.

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 an 8-parameter, no-output-schema calculation tool, the description covers purpose, legal basis, gross-basis assumption and the key parameter trap. It does not describe the returned result (single figure vs. itemized breakdown) or how ucreteDahilMaddesi/sozlesmeHaftalikSaat interact, though the schema documents those fields.

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 100%, so the baseline is 3, but the description earns an extra point by explicitly disambiguating haftalikCalisilanSaat: it is the week's total hours including normal hours (e.g. 52), not only overtime hours — a genuine misinterpretation risk the schema text alone only partly covers.

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 (weekly overtime pay calculation) and enumerates scope: general holiday work, weekly rest day work, and the 270-hour annual cap, plus the legal basis (4857 art. 41). This is clearly distinguishable from the payroll/tax calculators in the sibling list without opening the schema.

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 implied by the legal context (weekly overtime pay for an employee under Turkish labor law), but the description never states when to use this versus related tools such as brut_net_maas_hesapla or isten_ayrilma_alacaklari_hesapla, nor any preconditions 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