Skip to main content
Glama

Israeli Real Estate and Legal Calculators

apartment purchase costs

apartment_purchase_costs
Read-only

Estimated total additional costs of buying an apartment in Israel: purchase tax, lawyer fees, brokerage, registration fees, appraiser, inspector and more. 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": {
      "price": "<price>",
      "date": "<date>"
    },
    "name": "apartment_purchase_costs"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate, YYYY-MM-DD
langNoLanguage of the result (default he)
typeNoused = second-hand (default), dev = from a developer
buyerNoFor purchase tax: single = only apartment (default), additional = additional apartment
otherNoILS (optional)
priceYesApartment price, ILS
shareNoShare purchased, % (default 100)
mortgageNo
appraiserNoILS (optional)
inspectorNoILS (optional)
registrationNo
broker_percentNoBrokerage, % before VAT (optional)
lawyer_percentNoLawyer fee, % of price before VAT
mortgage_advisorNoILS (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 safety is covered; the description adds useful provenance by disclosing that results come from the official dira-law.co.il calculator, which explains the 'Estimated' qualifier. It does not disclose anything about output shape, precision, or how omitted optional parameters are defaulted by the calculator.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly packed sentences with the cost scope front-loaded and provenance second. The trailing 'and more' is mildly vague but signals that the enumeration is not exhaustive, which is honest rather than wasteful.

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 14-parameter tool with no output schema, the definition should clarify whether the return is a single total or an itemized breakdown, and how optional inputs (other, appraiser, inspector, mortgage_advisor) are treated when omitted. Provenance and cost scope are covered, but the result contract is left 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?

With 86% schema description coverage, the schema already explains nearly every parameter (lang, type, buyer, share, broker_percent, lawyer_percent, etc.). The description only maps loosely onto cost categories and adds nothing about the consequential enums like type (used/dev) or buyer (single/additional) that materially change purchase tax; baseline 3 applies.

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?

The description names a specific verb+resource ('Estimated total additional costs of buying an apartment in Israel') and enumerates the cost components included (purchase tax, lawyer fees, brokerage, registration, appraiser, inspector), which implicitly distinguishes it from the narrower sibling purchase_tax. It stops short of explicitly stating that it is the aggregate alternative to purchase_tax, so it is clear but not sibling-differentiating.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use statement, no exclusions, and no routing advice toward purchase_tax or capital_gains_tax for narrower or related questions. The agent must infer the use case (whole-deal closing cost estimation) purely from the scope sentence.

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