Skip to main content
Glama

Israeli Real Estate and Legal Calculators

construction index linkage

construction_index_linkage
Read-only

Linkage of payments to a developer to the Israeli construction inputs index (madad tsumot habniya) under the Sale (Apartments) Law amendment: only 50% of each payment is linked, the cap at the contractual delivery date. 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": {
      "contract_date": "<contract_date>",
      "price": "<price>",
      "delivery_date": "<delivery_date>",
      "payments": "<payments>"
    },
    "name": "construction_index_linkage"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the result (default he)
priceYesApartment price in the contract, ILS
paymentsYes
base_indexNoBase index (optional)
contract_dateYesDate, YYYY-MM-DD
delivery_dateYesContractual delivery date, YYYY-MM-DD
linked_share_percentNoLinked share of each payment under the contract, % (0-50, default 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 substantive behavior beyond that by stating the 50%-of-each-payment rule, the cap at the contractual delivery date, and that results come from the official dira-law.co.il calculator (i.e., an authoritative, deterministic computation). It omits latency/availability expectations, and 'runs the official calculator' sits in mild tension with openWorldHint=false, though it reads as an internal deterministic computation rather than an arbitrary external fetch.

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 dense sentences, front-loaded with the core rule and followed by the computation source; nothing is filler. Phrasing is slightly clunky ('Linkage of payments to a developer to the ... index'), which costs a point against a perfect score.

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 7-parameter financial calculation with no output schema, the agent still doesn't know the shape of the result (per-payment linked amounts, totals, index values used) or what base_index does. The statutory rule and data source are well covered, but the return side and one parameter remain underspecified.

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 86%, so the schema already documents price, dates, payments and lang; baseline is 3. The description does add meaning for linked_share_percent (the 50% default is the statutory norm) and delivery_date (the cap point), but it says nothing about base_index, the optional parameter whose schema text is only 'Base index (optional)'.

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 precise operation and resource: linking a developer's payments to the Israeli construction inputs index (madad tsumot habniya) under the Sale (Apartments) Law amendment, including the 50% linkage rule. That is far more specific than a generic 'linkage' tool. It stops short of 5 because it never contrasts itself with the sibling interest_and_linkage, which an agent could plausibly confuse with this one.

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

Usage Guidelines4/5

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

Applicability is clearly framed: payments to a developer under the Sale (Apartments) Law amendment, capped at the contractual delivery date, so an agent can judge the fact pattern that selects this tool. There are no explicit exclusions or named alternatives, which keeps it below 5, but the legal-scope statement gives real routing context.

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