Skip to main content
Glama

Israeli Real Estate and Legal Calculators

interest and linkage

interest_and_linkage
Read-only

Linkage differentials and interest on a judgment debt under the Israeli Adjudication of Interest and Linkage Law (including the 2026 amendment rules): CPI linkage and statutory interest per period. Runs the official calculator of il-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": {
      "decision_date": "<decision_date>",
      "amounts": "<amounts>"
    },
    "name": "interest_and_linkage"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the result (default he)
amountsYes
end_dateNoCommon end date (default: today), YYYY-MM-DD
decision_dateYesDate of the judgment/decision that set the debt, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 genuinely useful behavior context: results are broken out per period, the 2026 amendment rules are applied, and computation follows the official il-law.co.il calculator. It does not explain what the response contains (no output schema exists) or how edge cases like future end dates are treated.

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 sentences, front-loaded with the legal domain and scope, with no filler. The final sentence about the official calculator earns its place by establishing provenance and trust in the computation.

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 moderately complex financial-calculation tool with a nested amounts array and no output schema, the description omits what is returned (a total, a per-period table, per-amount breakdowns) and any precision or rounding behavior. It is enough to select the tool but leaves an agent uncertain about the result shape.

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 75%, so the schema does most of the work, including enum meanings for track and kind. The description adds only a light gloss ('CPI linkage and statutory interest per period') and does not clarify the interaction between decision_date, per-amount start/end, and the common end_date default — the one area where the schema alone is ambiguous.

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 gives a specific verb-and-resource pair: computing 'linkage differentials and interest on a judgment debt' under a named statute (Israeli Adjudication of Interest and Linkage Law) and its 2026 amendment. It is clearly distinguishable from siblings like construction_index_linkage or purchase_tax, though it does not explicitly name any sibling it is not.

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 domain — judgment-debt linkage and statutory interest — but there is no explicit when-to-use versus alternatives guidance and no stated prerequisites (e.g., when to prefer this over construction_index_linkage). An agent can infer the context but must reason about it rather than read it.

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