Skip to main content
Glama

Kira geliri vergisi

kira_geliri_vergisi_hesapla
Read-onlyIdempotent

Konut kira gelirinin 2026 gelir vergisini hesaplar (58000 TL istisna, götürü gider): beyan gerekip gerekmediği, taksitler, efektif oran. İşyeri kirası ve gerçek gider kapsam dışı.

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": {
      "aylikKira": "<aylikKira>"
    },
    "name": "kira_geliri_vergisi_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
kiraAyiNoKira alınan ay. Varsayılan 12.
aylikKiraYesTL.
istisnaEngeliNoKonut istisnası kullanılamıyor mu (ör. ticari kazanç beyanı). Varsayılan false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / aylikKira / description
      Previous value: -"Aylık brüt kira (TL)."New value: +"TL."
    • changedInput schema / properties / istisnaEngeli / description
      Previous value: -"Konut istisnasından yararlanılamıyor mu (ticari/serbest meslek kazancı beyanı ya da istisna sınırını aşan toplam gelir)? Varsayılan false."New value: +"Konut istisnası kullanılamıyor mu (ör. ticari kazanç beyanı). Varsayılan false."
    • changedInput schema / properties / kiraAyi / description
      Previous value: -"2026 yılında kira alınan ay sayısı. Varsayılan 12."New value: +"Kira alınan ay. Varsayılan 12."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish a pure-read, idempotent, closed-world calculator, so the description is not obligated to re-explain safety. It adds real value by naming the outputs the agent will receive (whether a declaration is required, installment structure, effective rate) and by fixing the tax year and exemption amount, which are the inputs' hidden assumptions. It does not state what happens to the effective-rate figure when the istisnaEngeli flag is flipped, which would have earned 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: the first carries the computation, year, exemption and method; the second carries the negative scope. Nothing is repeated from the title 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.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description steps in to enumerate the return payload (declaration requirement, installments, effective rate), and the year/method assumptions are fixed. The one remaining ambiguity for a tax tool with a boolean opt-out parameter is how the exemption-blocking case changes the reported figures, which the description leaves implicit.

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 baseline is 3. The description corroborates the model's semantics by naming the 58000 TL exemption and the götürü gider assumption, but it adds no per-parameter detail (e.g. how partial-year kiraAyi interacts with the annual exemption) beyond what the schema's own descriptions already say.

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 and resource ("Konut kira gelirinin 2026 gelir vergisini hesaplar") and pins the scope with concrete method details (58000 TL istisna, götürü gider). The closing clause explicitly rules out workplace rent and actual-expense method, so the agent can distinguish it from neighbouring calculators like kira_artis_hesapla without opening a 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?

Clear about the domain in which it applies (residential rent, lump-sum expense basis, 2026) and explicit about when NOT to use it (workplace rent, actual-expense deductions). What it lacks is a pointer to any specific alternative tool for those excluded cases, so the agent must infer the route itself.

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