Skip to main content
Glama

Memur ve emekli zammı

memur_emekli_zammi_hesapla
Read-onlyIdempotent

Ocak 2027 memur zammını (toplu sözleşme + enflasyon farkı) ve SSK/Bağ-Kur emekli zammını açıklanan TÜFE ile hesaplar; açıklanmamış aylarda tahmin kullanır ve kesin olup olmadığını söyler.

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": {
      "mevcutMaas": "<mevcutMaas>"
    },
    "name": "memur_emekli_zammi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
mevcutMaasYesAylık net maaş ya da emekli aylığı (TL).
tahminiAylikEnflasyonNoAçıklanmamış aylar için aylık TÜFE (%). Varsayılan 2.58.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / mevcutMaas / description
      Previous value: -"Şu anki aylık net maaş ya da emekli aylığı (TL)."New value: +"Aylık net maaş ya da emekli aylığı (TL)."
    • changedInput schema / properties / tahminiAylikEnflasyon / description
      Previous value: -"Açıklanmamış aylar için aylık TÜFE tahmini (%). Varsayılan son açıklanan ay (2.58)."New value: +"Açıklanmamış aylar için aylık TÜFE (%). Varsayılan 2.58."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description does add real behavioral value beyond them: it falls back to an estimate for unpublished months and reports whether the result is definitive. That uncertainty reporting is the most useful sentence in the definition; the gap is that it does not say what happens for periods other than Ocak 2027.

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 with the calculation target front-loaded and the estimate caveat trailing. Every clause carries information, though the parenthetical and the semicolon-joined fallback clause make it slower to parse than a two-sentence split would be.

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?

No output schema exists, so the description should signal the return shape; it does so partially by promising a definitive/estimate verdict, which is the key output distinction for this tool. It does not describe the returned breakdown (raise components, amounts), a minor remaining gap for a two-parameter calculator.

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 100%, so both parameters (mevcutMaas, tahminiAylikEnflasyon) are fully documented, including the 2.58 default and the -10/30 bounds. The description adds only that the calculation is net salary/pension and uses announced CPI, which is marginal beyond the schema — baseline 3 applies.

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?

States a specific verb (hesaplar) with a tightly bounded resource: the Ocak 2027 memur raise (collective agreement + inflation differential) and the SSK/Bağ-Kur retiree raise. The scope is specific enough to separate it from siblings like asgari_ucret_zammi_hesapla or enflasyon_etkisi_hesapla without needing to name them.

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?

Conveys the operating context implicitly: it is for January 2027 civil-servant and retiree raises, and it falls back to estimation for months whose CPI is not yet published. However, it never states when to prefer it over the neighbouring raise/inflation calculators, nor any exclusions, so the agent must infer the boundary from the tool name.

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