Skip to main content
Glama

Semerenko Group Public Site MCP

Cities with listings

sem.list_property_cities
Read-only

Every city that has published listings, with counts for sale, rent and short term and the canonical market page URL (or null if none). Use it to pick a valid city value.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 the safety profile is covered structurally. The description adds genuine value by disclosing the return content (counts per segment, canonical URL, explicit null when no page exists), but says nothing about list size, ordering, or whether results are filtered to published-only markets at scale.

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?

Two sentences, front-loaded with what is returned and followed by the actionable directive. No filler, no restatement of the title, and the null-case is handled inline.

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 the burden of describing results and does so adequately: counts by segment plus the market URL and its null case. Minor gaps remain around ordering and pagination, but for a parameterless read-only enumeration this is close to sufficient.

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?

The tool takes zero parameters, so there is no per-parameter meaning for the description to supply and the baseline applies. The schema is empty and fully consistent with the parameterless nature described.

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?

The description names a specific resource (cities that have published listings) and states exactly what each entry carries: sale/rent/short-term counts and a canonical market page URL. That is enough to tell it apart from lookup tools like sem.get_property, though it never explicitly contrasts itself with the similarly named sem.market_cities sibling.

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?

'Use it to pick a valid city value' gives clear positive guidance, framing the tool as a lookup/enumeration step that feeds other calls. It stops short of stating exclusions or naming an alternative when a different city source is preferred, so it is clear context rather than full when/when-not guidance.

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