Skip to main content
Glama

Israeli Real Estate and Legal Calculators

purchase tax

purchase_tax
Read-only

Israeli purchase tax (mas rechisha) on buying real estate: apartment, land, business property or farm. Uses the brackets in force on the transaction date (Land Taxation Law s.9 and the Tax Authority instructions). Runs the official calculator of dira-law.co.il.

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": {
      "value": "<value>",
      "date": "<date>"
    },
    "name": "purchase_tax"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate, YYYY-MM-DD
dealNosale = purchase for consideration (default), gift = transfer without consideration from a relative, spouse = transfer of a residential apartment without consideration to a spouse living in it
langNoLanguage of the result (default he)
assetNores = residential apartment (default), land = land/plot, biz = business property, farm = agricultural farm
buyerNoFor residential: single = only apartment (default), additional = additional apartment, oleh = new immigrant, foreign = foreign resident, disabled = disabled person / victim of hostilities / bereaved family
valueYesValue of the property / consideration in ILS (from a developer: including VAT)
replacement_apartmentNoSingle apartment bought as a replacement while still owning the previous one (to be sold within the statutory period)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that – bracket version is keyed to the transaction date per Land Taxation Law s.9, and the result comes from the official dira-law.co.il calculator – but it says nothing about what is returned (tax amount, breakdown, currency) despite there being no output schema. The mention of running an external calculator also sits somewhat awkwardly against openWorldHint=false, though it reads as a fixed computation rather than open-ended exploration.

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 front-loaded sentences with no filler: first the tax and its asset scope, then the legal basis and data source. Every clause carries information an agent can use.

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?

For a read-only calculation with a fully documented 7-parameter schema, the definition covers purpose, legal basis, and date sensitivity adequately. The main residual gaps are the shape of the result (no output schema exists) and routing against overlapping cost/tax siblings.

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% with enum values fully documented, so the schema carries the parameter burden. The description reinforces the date parameter's significance (brackets in force on the transaction date) but adds no meaning to deal, buyer, asset, or replacement_apartment beyond what the schema already states.

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?

Names a specific tax (Israeli purchase tax / mas rechisha) with a specific resource scope enumerated as apartment, land, business property, or farm, and states the calculation basis. That is enough to distinguish it from cost-side siblings like apartment_purchase_costs or capital_gains_tax 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 Guidelines3/5

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

Usage is implied rather than stated: the tool applies to a real-estate purchase on a given transaction date. It never says when to choose it over apartment_purchase_costs or capital_gains_tax, nor whether gift/spouse deals are in-scope or a separate tool, so the agent must infer routing.

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