Skip to main content
Glama

Semerenko Group Public Site MCP

Israel property investment score

sem.calc_invest_score
Read-only

Scores a budget + goal + Israeli city against the Semerenko market dataset (nadlan.gov.il Israel Tax Authority transactions, 203 cities). Returns the 0-100 fit score, citywide benchmark price/rent/yield, purchase tax estimate, and verdict. Use sem.market_cities for the exact city list.

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": {
      "budget": "<budget>",
      "goal": "<goal>",
      "city": "<city>"
    },
    "name": "sem.calc_invest_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesAny of the 203 Israeli benchmark cities, English name (e.g. Tel Aviv-Yafo, Netanya, Ra'anana)
goalYesWhat the buyer wants to do
budgetYesTotal budget in ILS (500,000 - 15,000,000)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and a closed-world dataset, so the safety profile is covered. The description adds genuinely useful context beyond that: the authoritative data provenance, the dataset size, and the exact shape of the returned values, which no annotation conveys. It does not discuss latency, cost, or failure behavior for out-of-range budgets, keeping 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?

Three sentences, no filler: purpose and data source first, then the concrete return set, then the prerequisite pointer. Every sentence earns its place and the most decision-relevant information is front-loaded.

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?

There is no output schema, but the description compensates by enumerating the returned fields (0-100 fit score, benchmark price/rent/yield, purchase tax estimate, verdict). Combined with annotations covering the safety profile and a fully documented three-parameter schema, an agent has everything needed to call it correctly.

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 coverage is 100%, with each parameter documented including the ILS budget range, the three-value goal enum, and city naming conventions, so the schema already carries the semantic load. The description restates the triple as 'budget + goal + city' without adding format, defaulting, or edge-case guidance beyond the schema. Baseline 3 applies.

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 names a specific verb and resource ('scores a budget + goal + Israeli city') and pins the data source to the Semerenko market dataset with nadlan.gov.il Israel Tax Authority transactions across 203 cities. It also enumerates the concrete outputs (fit score, benchmark price/rent/yield, purchase tax estimate, verdict), so an agent can distinguish it from research-style siblings 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 Guidelines4/5

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

It gives a clear usage context and an explicit prerequisite pointer: 'Use sem.market_cities for the exact city list' guards against invalid city input. It stops short of stating when to prefer this over the similarly named sem.ai_investment_simulator_research or other research tools, so no exclusions or routing rules are provided.

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