Skip to main content
Glama

Miras payı

miras_payi_hesapla
Read-onlyIdempotent

Türk Medeni Kanunu'na göre yasal miras ve saklı payları (kesir, yüzde; tereke verilirse TL) ve tasarruf nisabını hesaplar. Vasiyet, feragat ve ret hariç.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "miras_payi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
esSagNoVarsayılan false.
terekeNoMiras tutarı (TL).
anneSagNoVarsayılan false.
babaSagNoVarsayılan false.
buyuklerNoSağ büyükanne ve büyükbabalar.
tamKardesNoVarsayılan 0.
cocukSayisiNoSağ çocuk (evlatlık dahil). Varsayılan 0.
anaBirKardesNoVarsayılan 0.
babaBirKardesNoVarsayılan 0.
olenCocuklarinCocuklariNoÖnce ölen her çocuğun sağ çocuk sayısı, ör. [2, 1].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / anaBirKardes / description
      Previous value: -"Ana bir kardeş sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / anneSag / description
      Previous value: -"Anne sağ mı? Yalnız çocuk ve torun yoksa önemlidir. Varsayılan false."New value: +"Varsayılan false."
    • changedInput schema / properties / babaBirKardes / description
      Previous value: -"Baba bir kardeş sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / babaSag / description
      Previous value: -"Baba sağ mı? Yalnız çocuk ve torun yoksa önemlidir. Varsayılan false."New value: +"Varsayılan false."
    • changedInput schema / properties / buyukler / description
      Previous value: -"Yalnız 1. ve 2. zümre yoksa önemlidir: sağ olan büyükanne ve büyükbabalar."New value: +"Sağ büyükanne ve büyükbabalar."
    • changedInput schema / properties / cocukSayisi / description
      Previous value: -"Sağ çocuk sayısı (evlatlık ve evlilik dışı dahil). Varsayılan 0."New value: +"Sağ çocuk (evlatlık dahil). Varsayılan 0."
    • changedInput schema / properties / esSag / description
      Previous value: -"Vefat edenin eşi sağ mı? Varsayılan false."New value: +"Varsayılan false."
    • changedInput schema / properties / olenCocuklarinCocuklari / description
      Previous value: -"Vefat edenden önce ölmüş her çocuğun sağ çocuk sayısı, ör. [2, 1]. Yoksa boş."New value: +"Önce ölen her çocuğun sağ çocuk sayısı, ör. [2, 1]."
    • changedInput schema / properties / tamKardes / description
      Previous value: -"Anne-baba bir kardeş sayısı. Varsayılan 0."New value: +"Varsayılan 0."
    • changedInput schema / properties / tereke / description
      Previous value: -"İsteğe bağlı: paylaştırılacak miras tutarı (TL)."New value: +"Miras tutarı (TL)."
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in what it discloses: the governing legal code and the conditional output unit (TL only when an estate amount is supplied). It does not describe the returned structure or how defaults behave, which keeps it from a 5.

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, zero filler: the legal basis and computed outputs come first, the exclusions last. Nothing is repeated from the schema and no sentence could be dropped without losing information.

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 ten-parameter tool with a nested object and no output schema, the description omits two things an agent would want: that every parameter is optional (so an empty call is legal) and what the response looks like beyond units. The legal basis and scope exclusions are covered, so it is adequate but not fully self-sufficient.

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 the ten parameters and their defaults are already documented, and the baseline is 3. The description adds one piece of meaning the schema lacks — that "tereke" switches results to TL — but says nothing about the nested "buyukler" object or the interplay of optional heir flags.

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 ("hesaplar") and specific resources ("yasal miras ve saklı paylar", "tasarruf nisabı") within an explicitly stated legal framework ("Türk Medeni Kanunu'na göre"). It also declares the output form (kesir, yüzde, or TL), which no sibling calculator shares, so the domain alone separates it from the other "*_hesapla" tools.

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?

"Vasiyet, feragat ve ret hariç" gives a concrete exclusion boundary telling the agent which estate scenarios this tool does not model. It does not name an alternative tool or state prerequisites, but the exclusions are a real usage constraint rather than an implied one.

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