Skip to main content
Glama

Tapu harcı

tapu_harci_hesapla
Read-onlyIdempotent

Taşınmaz satışında alıcı ve satıcının tapu harcını hesaplar (492 s. Harçlar Kanunu). Matrah, satış bedeli ile emlak vergisi değerinden yükseğidir.

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": {
      "satisBedeli": "<satisBedeli>"
    },
    "name": "tapu_harci_hesapla"
  }
}

Input Schema

NameRequiredDescriptionDefault
satisBedeliYesSatış bedeli (TL).
donerSermayeNoDöner sermaye ücreti (TL).
emlakVergisiDegeriNoEmlak vergisi değeri (TL).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / donerSermaye / description
      Previous value: -"Tapu müdürlüğü döner sermaye ücreti (TL). Bilinmiyorsa boş."New value: +"Döner sermaye ücreti (TL)."
    • changedInput schema / properties / emlakVergisiDegeri / description
      Previous value: -"Belediyeden alınan emlak vergisi değeri (TL). Bilinmiyorsa boş."New value: +"Emlak vergisi değeri (TL)."
    • changedInput schema / properties / satisBedeli / description
      Previous value: -"Beyan edilen satış bedeli (TL)."New value: +"Satış bedeli (TL)."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine value with the legal basis (Law 492) and the matrah rule that governs which figure is taxed. It does not disclose the applicable rate, whether the rate differs for buyer versus seller, or what the computed response contains.

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 short sentences, both front-loaded: the first defines the operation and its legal basis, the second delivers the one non-obvious computational rule. There is no filler or restatement of the tool name.

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?

With no output schema, the description is the only place where return content could be described, yet it never says that separate buyer and seller amounts are produced or how the round figure is presented. It also leaves donerSermaye unexplained relative to the others. For a three-parameter read-only calculator it is workable but not fully complete.

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%, so the baseline would be 3, but the description goes beyond the field labels by explaining the interaction between satisBedeli and emlakVergisiDegeri — the taxable base is whichever is higher. That relationship is not derivable from the schema alone. The third parameter, donerSermaye, is not addressed in the description, which keeps it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: calculating the title deed fee (tapu harcı) for both buyer and seller in a real-estate sale, with the governing law cited. The resource is concrete enough to separate it from the other calculators in the sibling list, which cover tax, salary, interest and date topics, though no sibling is named explicitly.

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?

Usage is implied rather than spelled out: an agent can infer the tool applies to property sales, and the description usefully states that the assessment base is the higher of the sale price and the property tax value. There is no explicit when-to-use, when-not-to-use, or named alternative, and nothing tells the agent whether this replaces or complements a separate tax calculation.

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