Skip to main content
Glama

Semerenko Group Public Site MCP

Israel seller net proceeds calculator

sem.calc_seller_net_proceeds
Read-only

Computes estimated net proceeds for selling an Israeli home: agent fee with 18% VAT, legal costs, estimated mas shevach (25% of the CPI-indexed real gain, with the only-home exemption and its ₪5,008,000 ceiling), mortgage payoff, and other costs.

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": {
      "salePrice": "<salePrice>"
    },
    "name": "sem.calc_seller_net_proceeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
miscNoMoving and other costs in ILS
legalNoLegal and closing costs in ILS (default 18000)
taxesNoBetterment levy or other taxes in ILS
agentPctNoAgent fee percent before VAT (default 2)
expensesNoDocumented deductible expenses in ILS
onlyHomeNoIs this the seller's only home (default yes)
salePriceYesExpected sale price in ILS (required)
purchaseYearNoYear purchased, 2000-2026 (default 2015)
prepayPenaltyNoEarly mortgage repayment penalty in ILS
purchasePriceNoOriginal purchase price in ILS
mortgagePayoffNoRemaining mortgage to pay off in ILS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and non-destructive/closed-world behavior, so the bar is lower, and the description still adds real substance: the 18% VAT on the agent fee, the 25% mas shevach rate applied to the CPI-indexed real gain, the only-home exemption with a ₪5,008,000 ceiling, and the "estimated" framing. It does not disclose the shape of the returned result or the assumptions/defaults behind the estimate, which keeps it short of a 5.

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?

A single front-loaded sentence with the core action first and the itemized cost components after; every clause carries domain information and there is no filler or repetition of the title.

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?

With 11 parameters, several defaults, and no output schema, the description explains the calculation components well but never says what the tool returns (a net figure, or a line-item breakdown) or which defaults apply to unset inputs. For a read-only calculator this is adequate, but the absence of any return-value framing leaves a real gap given there is no output schema to cover it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds semantics the schema cannot: that agentPct is quoted before VAT and VAT is applied on top, and that onlyHome triggers an exemption capped at ₪5,008,000, which explains the interaction between parameters rather than restating them. It does not disambiguate overlapping fields such as expenses vs. taxes vs. misc, so it stops at 4.

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 and resource ("Computes estimated net proceeds for selling an Israeli home") and immediately enumerates the components netted out (agent fee + VAT, legal, mas shevach, mortgage payoff, other costs). This is far more specific than the name alone and clearly separates it from the research/list/get siblings in the catalog.

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 only implied by the domain framing (a seller estimating proceeds from a sale); there is no explicit "use when" clause, no statement about when not to use it, and no pointer to any alternative calculator such as sem.calc_invest_score or sem.list_calculators. An agent can infer the scenario, but the description does no active 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