Skip to main content
Glama

Semerenko Group Public Site MCP

Israel Rental Yield AI Research

sem.ai_rental_yield_research
Read-only

Runs live web-backed rental yield research for an Israeli city or area: current rent and sale comparables, one gross yield number, confidence, strong/weak points, and source URLs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sem.ai_rental_yield_research"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional neighborhood
cityNoIsraeli city, e.g. Netanya
queryNoFree-text scenario if city is unknown
roomsNoOptional room count, e.g. 3 or 4
monthlyRentNoOptional anchor monthly rent in ILS
propertyTypeNoOptional property type (default Residential apartment)
purchasePriceNoOptional anchor purchase price in ILS

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety and open-web scope are covered structurally. The description adds real value beyond that by disclosing the return shape (a single gross yield number plus confidence and source URLs), which signals an estimate with uncertainty rather than a precise figure. It says nothing about latency, failure modes when no comparables are found, or freshness of the web sources.

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?

A single front-loaded sentence with no filler, and the output list is packed into a compact clause. It is dense but readable; slightly more structure (splitting inputs vs. outputs) would improve scanning.

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

Completeness4/5

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

With no output schema, the description carries responsibility for describing returns and it does so explicitly, including confidence and source URLs. The main gap is that all seven parameters are optional, yet the description never states a minimum requirement (city or query) for a meaningful result.

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 100%, with all seven parameters individually documented (city, area, query, rooms, monthlyRent, purchasePrice, propertyType), so the baseline of 3 applies. The description adds no parameter-level meaning — notably it never clarifies that rental anchors are optional or how the free-text query relates to city.

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?

States a specific verb (runs research) and resource (rental yield for an Israeli city/area), then enumerates the concrete deliverables: rent and sale comparables, one gross yield number, confidence, strong/weak points, source URLs. An agent can tell this is an estimation/research tool rather than a calculator or listing lookup. It stops short of naming a sibling it replaces (e.g. mortgage or investment simulator research).

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 phrase 'live web-backed rental yield research' — the agent can infer this is for yield estimation when a city or area is known. There is no explicit when-to-use/when-not guidance and no statement of prerequisites, cost, or latency, even though the sibling set contains adjacent research tools that could be confused with 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