Skip to main content
Glama

Rapor parası

rapor_parasi_hesapla
Read-onlyIdempotent

SGK rapor parasını (geçici iş göremezlik ödeneği) hesaplar: hastalık, iş kazası ve doğum (analık); 4/a sigortalılar. ÖNEMLİ: tur hastalik ya da is-kazasi ise raporGun da verilmelidir; analikte gerekmez.

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": {
      "tur": "<tur>",
      "ucAylikKazanc": "<ucAylikKazanc>"
    },
    "name": "rapor_parasi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
turYesanalik: doğum.
tedaviNoVarsayılan ayakta.
raporGunNoRapordaki gün. hastalik ve is-kazasi için ZORUNLU.
cogulGebelikNoDoğumda. Varsayılan false.
ucAylikKazancYesSon 3 ayın prime esas brüt kazanç toplamı (TL).
yillikPrimGunNoSon 1 yıldaki prim günü. Varsayılan 360.
calisilanHaftaNoDoğumda: doğumdan önce çalışılan hafta. Varsayılan 0.
ucAylikPrimGunNoVarsayılan 90.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / calisilanHafta / description
      Previous value: -"Doğumda: hekim onayıyla doğumdan önce çalışılan hafta (0-2). Varsayılan 0."New value: +"Doğumda: doğumdan önce çalışılan hafta. Varsayılan 0."
    • changedInput schema / properties / cogulGebelik / description
      Previous value: -"Doğumda çoğul gebelik mi? Varsayılan false."New value: +"Doğumda. Varsayılan false."
    • changedInput schema / properties / raporGun / description
      Previous value: -"Rapordaki gün sayısı (1-540). tur hastalik ya da is-kazasi ise ZORUNLU; analikte kullanılmaz."New value: +"Rapordaki gün. hastalik ve is-kazasi için ZORUNLU."
    • changedInput schema / properties / tedavi / description
      Previous value: -"Ayakta ya da hastanede yatarak tedavi. Varsayılan ayakta."New value: +"Varsayılan ayakta."
    • changedInput schema / properties / tur / description
      Previous value: -"hastalik, is-kazasi ya da analik (doğum)."New value: +"analik: doğum."
    • changedInput schema / properties / ucAylikKazanc / description
      Previous value: -"Rapordan önceki son 3 ayın prime esas brüt kazanç toplamı (TL)."New value: +"Son 3 ayın prime esas brüt kazanç toplamı (TL)."
    • changedInput schema / properties / ucAylikPrimGun / description
      Previous value: -"O 3 aydaki prim günü. Varsayılan 90."New value: +"Varsayılan 90."
    • changedInput schema / properties / yillikPrimGun / description
      Previous value: -"Rapordan önceki 1 yıldaki prim günü (hastalık ve doğumda şart). Varsayılan 360."New value: +"Son 1 yıldaki prim günü. Varsayılan 360."
  2. Changed1 schema field changed
    • changedInput schema / properties / raporGun / description
      Previous value: -"Rapor gün sayısı (hastalık ve iş kazasında zorunlu)."New value: +"Rapordaki gün sayısı (1-540). tur hastalik ya da is-kazasi ise ZORUNLU; analikte kullanılmaz."
  3. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the agent knows this is a safe, deterministic computation. The description adds the domain restriction (4/a) and the conditional required-parameter behavior, but says nothing about the calculation basis, rounding, or what the response contains. With four annotation hints already carrying the safety profile, this is a modest addition.

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: purpose and scope first, then the critical conditional requirement flagged with 'ÖNEMLİ'. Every clause carries information and the most error-prone constraint is front-loaded where an agent will see it.

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 an 8-parameter calculator with no output schema, the definition covers purpose, scope, and the key conditional requirement, but never says what is returned (a TL benefit amount, and whether it is gross or net) or how the optional inputs (tedavi, cogulGebelik, calisilanHafta) influence the outcome. The schema fills the parameter gaps, but the return-value gap remains since no output schema exists.

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 8 parameters is already documented, including the 'ZORUNLU' note on raporGun. The description's conditional sentence largely restates that schema-level constraint rather than adding new meaning (e.g. how ucAylikKazanc or yillikPrimGun affect the result). Baseline 3 applies when the schema does the heavy lifting.

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) and a precisely named resource (SGK rapor parası / geçici iş göremezlik ödeneği), then narrows the scope to three case types (hastalık, iş kazası, analık) and 4/a insured. This is enough to separate it from the other payroll/benefit 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes clear when the tool applies: only for 4/a insureds and only for the three enumerated benefit types, with an explicit conditional rule that raporGun must be supplied for hastalik/is-kazasi but not for analik. It stops short of naming a sibling alternative or stating exclusions (e.g. 4/b or 4/c insureds), so it is clear context rather than full routing guidance.

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