Skip to main content
Glama

Kira artışı

kira_artis_hesapla
Read-onlyIdempotent

Konut kirası yenileme artışını hesaplar. Yasal tavan (TBK md. 344) TÜFE'nin on iki aylık ortalamasıdır; istenen oran aşarsa tavan uygulanır.

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": {
      "mevcutKira": "<mevcutKira>"
    },
    "name": "kira_artis_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
mevcutKiraYesŞu anki aylık kira (TL).
istenenOranNoİstenen artış (%). Boşsa yasal tavan.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / istenenOran / description
      Previous value: -"Ev sahibinin istediği artış oranı (%). Boş bırakılırsa güncel yasal tavan kadar artış hesaplanır."New value: +"İstenen artış (%). Boşsa yasal tavan."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already cover the safety profile (read-only, idempotent, non-destructive) and no open-world access, so the bar is lower. The description adds substantive behavior beyond them: it names the legal basis (TBK md. 344), defines the cap as the twelve-month average CPI, and states that an over-cap requested rate is silently reduced to the cap, which is a non-obvious side effect worth disclosing.

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, no filler: the purpose comes first, followed by the governing rule. Every clause carries information an agent cannot get from the annotations or schema.

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?

There is no output schema, so the description ideally should indicate what comes back (increase amount, new rent, applied rate, or the CPI figure used). It also does not say where the CPI average comes from or which reference month is used. The calculation rule is complete, but the result shape is left undefined.

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% and both parameters are documented, so the baseline is 3. The description earns one step more by explaining what happens when 'istenenOran' exceeds the ceiling, namely that the legal cap overrides it, which gives the parameter a consequence the schema alone does not convey.

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 opens with a specific verb plus a narrow resource: 'Konut kirası yenileme artışını hesaplar' (calculates the residential-rent renewal increase). The 'konut' (residential) qualifier and the renewal framing set it apart from the other single-purpose calculators in the sibling list without naming any of 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?

It explains the domain rule but never says when to reach for this tool rather than a related one (for example a commercial-rent or tax calculation), nor does it state prerequisites such as which CPI period will apply. Usage is inferable from the single-purpose name and the legal-cap note, but it is left to inference rather than stated.

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