Skip to main content
Glama

Semerenko Group Public Site MCP

Market data: one neighborhood

sem.market_neighborhood
Read-only

Market record for a neighborhood: sale/rent/yield (estimates labelled), per-size breakdown, amenities within 500m. Get slugs from sem.market_city.

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": {
      "city": "<city>",
      "neighborhood": "<neighborhood>"
    },
    "name": "sem.market_neighborhood"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYes
neighborhoodYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds behavior the annotations cannot: that figures are estimates and labelled as such, that there is a per-size breakdown, and that amenities are scoped to a 500m radius. That is substantive context about what the agent will receive. It does not discuss data freshness, coverage limits, or error behavior for unknown slugs.

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?

Two short sentences, front-loaded with what the tool returns and followed by the input-source hint. No filler or repetition. The parenthetical '(estimates labelled)' is compact and informative.

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 must convey return content, and it does so concretely: price/rent/yield, size breakdown, nearby amenities. Inputs are covered well enough via the slug-source hint, and the read-only annotations cover the safety profile. Missing only edge-case behavior for invalid slugs or cities with no neighborhood data.

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 0%, so the description carries the burden. It does add real meaning by telling the agent both identifiers are slugs sourced from sem.market_city, which resolves format ambiguity. It does not, however, distinguish what 'city' means versus 'neighborhood' in slug terms, or what happens if the pair is mismatched, so compensation is partial.

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 the resource precisely ('Market record for a neighborhood') and enumerates the contents: sale/rent/yield with estimates labelled, per-size breakdown, amenities within 500m. It is clearly a retrieval tool, and the pointer to sem.market_city signals it is the neighborhood-level counterpart to the city-level tool. It does not explicitly contrast its scope against the city tool's contents, so it falls short of a 5.

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: 'Get slugs from sem.market_city' gives a prerequisite and routes the agent to the sibling that supplies inputs, which is genuinely useful. However, there is no statement of when to prefer this over sem.market_city or sem.market_cities, nor any exclusions or conditions. Adequate but with clear gaps.

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