Skip to main content
Glama

Semerenko Group Public Site MCP

Market data: list cities

sem.market_cities
Read-only

Live Semerenko market dataset: estimated median sale price, monthly rent and gross rental yield for 203 Israeli cities (standard-apartment headline, ILS), with page URLs. Optional name filter. Figures are Semerenko Group estimates derived from public transaction records - independent analysis, not official figures.

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.market_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax cities to return. Default 50.
searchNoOptional name filter (English or Hebrew).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine provenance context beyond that: figures are Semerenko Group estimates derived from public transaction records and are explicitly not official figures, plus the scope is capped at 203 cities. It still omits ordering, pagination behavior beyond the default, and response shape.

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?

Front-loaded with the dataset scope and headline metrics, then provenance caveat. Dense but every clause carries information; the repeated framing ('Semerenko' appears in both dataset name and attribution) is the only mild redundancy.

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 no output schema, the description takes on the burden of naming the returned fields (price, rent, yield, page URL), their units and basis (ILS, standard apartment), and the dataset ceiling. Combined with annotations and a fully documented two-parameter schema, an agent has everything needed to call it and interpret results.

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% and both parameters already carry descriptions (limit max 203 default 50; search English or Hebrew), so the baseline is 3. The description corroborates the optional name filter and ties the 203 ceiling to the dataset itself, giving the limit's maximum a concrete meaning.

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 ('list ... 203 Israeli cities') and enumerates the exact metrics returned (median sale price, monthly rent, gross rental yield, ILS, page URLs). An agent knows precisely what this yields and can infer it is the index-level counterpart to the singular sem.market_city.

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

Usage Guidelines2/5

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

The description explains what the tool returns but never says when to choose it over sem.market_city, sem.list_property_cities, or sem.market_neighborhood, and gives no exclusions or sequencing advice. The only usage-adjacent statement is that the name filter is optional, which is really parameter detail.

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