Israel Small Business Valuation (esek-shave)

הערכת שווי לעסק קטן בישראל

estimate_business_value

Read-onlyIdempotent

Estimates the market value in ILS of a specific small or mid-sized business in Israel, from its industry, annual revenue and annual pre-tax profit. Use this when someone asks what an Israeli business is worth or what price is fair for it: an owner selling or setting an asking price, a partner leaving or being bought out, a buyer checking whether an asking price makes sense, an accountant or broker preparing a number for a client, a bank or investor asking, or a divorce or inheritance that includes a business. Typical requests: "כמה שווה העסק שלי", "כמה לבקש על המסעדה", "הערכת שווי לעסק", "השותף רוצה לצאת, כמה לשלם לו", "מבקשים 800 אלף על בית הקפה, זה הוגן?", "what is my cafe in Tel Aviv worth". Covers restaurants and cafes, retail, professional services, clinics, beauty and barbershops, construction trades, education, logistics, events and tech services. Not for public companies, real estate, startups priced on a funding round, or businesses outside Israel. A profit range (annualProfitMin/annualProfitMax) works when exact profit is unknown. Returns the likely value, a low-high range, a confidence level, a Hebrew summary, the follow-up questions that would tighten the number, and a link to the full calculation on esek-shave.co.il. Method: Israeli industry multiples on owner profit (SDE), cross-checked with a revenue multiple, adjusted for owner salary, years in business and debt.

Input Schema

Name	Required	Description
`industry`	Yes	Industry, Hebrew name (e.g. מזון ומסעדנות) or English alias (restaurant, retail, clinic, dentist, services, accounting, tech, construction, plumber, beauty, salon, education, logistics, events, other). Send "other" if nothing fits.
`ownerSalary`	No	Annual salary the business pays the owner as an expense (company / בע"מ only), in ILS. It is added back to profit. For a sole proprietor (עוסק) the profit already includes the owner's earnings: send 0 or omit.
`yearsActive`	No	Optional. Years the business has been operating. If unknown, omit it: the estimate treats age as neutral and lists it as a follow-up question.
`annualProfit`	Yes	Annual pre-tax profit in ILS. Negative for a loss. If the owner only knows a rough range, send the midpoint here and the bounds in annualProfitMin / annualProfitMax.
`loansBalance`	No	Outstanding loans and supplier debt in ILS (optional, deducted). 0 = no debt.
`annualRevenue`	Yes	Annual revenue (turnover) in ILS, e.g. 2400000. If the owner gives a monthly figure, multiply by 12.
`annualProfitMax`	No	Optional. Upper bound of annual profit when the owner only knows a range.
`annualProfitMin`	No	Optional. Lower bound of annual profit when the owner only knows a range (e.g. 100000 for "100-200 thousand").

Output Schema

Name	Required	Description	Default
`ok`	Yes
`errors`	No
`summary`	No
`estimate`	No
`requestId`	No
`resultUrl`	No
`confidence`	No
`fullReport`	No
`lossMaking`	No
`nextQuestions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 5, 2026

changedInput schema / properties / annualRevenue / description

Previous value: -"Annual revenue in ILS. If the owner gives a monthly figure, multiply by 12."New value: +"Annual revenue (turnover) in ILS, e.g. 2400000. If the owner gives a monthly figure, multiply by 12."

changedInput schema / properties / yearsActive / description

Previous value: -"Years in operation (optional)"New value: +"Optional. Years the business has been operating. If unknown, omit it: the estimate treats age as neutral and lists it as a follow-up question."

Changed3 schema fields changedOct 4, 2026

changedInput schema / properties / annualProfit / description

Previous value: -"Annual pre-tax profit in ILS. Negative for a loss."New value: +"Annual pre-tax profit in ILS. Negative for a loss. If the owner only knows a rough range, send the midpoint here and the bounds in annualProfitMin / annualProfitMax."

addedInput schema / properties / annualProfitMax

Added value: +{
+  "description": "Optional. Upper bound of annual profit when the owner only knows a range.",
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / annualProfitMin

Added value: +{
+  "description": "Optional. Lower bound of annual profit when the owner only knows a range (e.g. 100000 for \"100-200 thousand\").",
+  "minimum": 0,
+  "type": "number"
+}

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description goes further by disclosing the valuation method (Israeli industry multiples on owner profit/SDE, cross-checked with a revenue multiple, adjusted for owner salary, years active and debt) and the shape of the result, which the annotations do not provide. No mention of rate limits or confidence caveats beyond the confidence level field.

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?

Purpose is front-loaded in the first sentence, followed by usage, examples, exclusions and method in a logical order. It is long, and the six quoted example requests are more volume than strictly necessary, but each section serves a distinct function rather than repeating the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, an explicit read-only annotation set, and 100% schema description coverage, the description needs only to add selection context — which it does thoroughly via triggers, exclusions and method. Nothing an agent needs in order to choose and call this tool is missing.

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; the description adds cross-parameter guidance beyond the schema by explaining that a profit range (annualProfitMin/annualProfitMax) is the fallback when exact profit is unknown, and that owner salary/years/debt adjust the number. It stops short of adding syntax or format detail the schema doesn't already carry.

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?

The description states a specific verb (estimates), resource (market value of a small/mid-sized Israeli business) and inputs (industry, revenue, pre-tax profit), and its scope is clearly separable from the sibling get_industry_multiples, which returns raw multiples rather than a computed valuation.

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

Usage Guidelines5/5

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

It enumerates concrete triggering situations (owner selling, partner buyout, buyer sanity-checking an asking price, accountant/broker, bank/investor, divorce/inheritance) and gives sample utterances, then explicitly excludes public companies, real estate, funding-round startups, and non-Israeli businesses — both when-to-use and when-not are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Israel Small Business Valuation (esek-shave) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?