Skip to main content
Glama

Israeli Real Estate and Legal Calculators

combination vs cash

combination_vs_cash
Read-only

Compares selling land for cash with a combination deal (land for apartments) with a developer, in present-value terms. 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>",
      "units": "<units>",
      "unit_value": "<unit_value>",
      "months": "<months>"
    },
    "name": "combination_vs_cash"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the result (default he)
rentNoRent from the developer during construction, ILS per month
priceYesCash price offered, ILS
unitsYesNumber of apartments received
monthsYesMonths to delivery
cash_taxNoLand appreciation tax in the cash sale, ILS
combo_taxNoTax in the combination deal, ILS
cash_costsNoCosts in the cash sale, ILS
unit_valueYesEstimated value of each apartment at delivery, ILS
combo_costsNoCosts in the combination deal, ILS
discount_rateNoAnnual discount rate, %
purchase_costNoCost of acquiring the property, ILS
land_share_soldNoShare of the land sold to the developer, %
pay_now_percentNo% paid at signing
months_to_balanceNoMonths to the balance payment
cash_from_developerNoCash payment from the developer, ILS
qualified_residence_exemptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 usefully adds that results come from the official dira-law.co.il calculator, implying authoritative output. It does not disclose how unspecified optional inputs are defaulted, whether the calculation is deterministic, or what the response contains. Note the mild tension between 'runs the official calculator of dira-law.co.il' and openWorldHint=false, though this reads as a fixed known endpoint rather than a contradiction.

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, front-loaded with the comparison being made and followed by the provenance of the calculation. 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?

The description makes clear what is computed, but for a 17-parameter financial model with no output schema, it never indicates what the result looks like (per-scenario present values, a delta, a recommendation) or how defaults are handled. Adequate to invoke, thin for interpreting the answer.

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 description coverage is 94%, so nearly all 17 parameters are already documented in the schema, and the description adds no parameter-level meaning. Baseline 3 applies since the schema carries the burden; the description could have flagged defaults for discount_rate or lang but does not.

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 (compares) and two precisely named resources (cash sale of land vs. a land-for-apartments combination deal) evaluated in present-value terms. The subject matter (land sale to a developer) is distinct enough from the tax/fee siblings that an agent can route to it 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 by the subject: an agent can infer it applies when a landowner is weighing cash against a combination deal. However, there is no explicit when-to-use framing, no prerequisites (e.g., that price, units, unit_value and months are mandatory), and no statement of which sibling to use for the tax-only side of the analysis.

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