Skip to main content
Glama

Deweloperuch MCP

Search investments

deweloperuch_search_investments
Read-only

Search investments (developer projects, primary market). Two modes: with city (full data) or with name alone (whole Poland; only investment_slug, name and offers_active, in the site's order). Use it when the question is about projects rather than single flats: e.g. the cheapest per m² in a city, the investments of one developer (city + developer_slug from deweloperuch_search_developers), the slug of an investment by its name. With city it returns the investments the site shows on the city's map (those with active offers; ones without may be missing) with averages over active offers; name and developer_slug narrow the list, sort orders it (default: most active offers; entries without an average come last). Offers and details of one investment come from deweloperuch_get_investment (investment_slug); a particular offer's price history from deweloperuch_get_offer. No price or area filter here — for those ranges use deweloperuch_get_market_statistics. city=polska does not work. These are developers' asking prices. Two kinds of prices must not be mixed: developers' asking prices (deweloperuch_search_investments, deweloperuch_get_investment, deweloperuch_get_offer, deweloperuch_get_market_statistics), RCN transaction prices (deweloperuch_estimate_property_value, deweloperuch_get_transaction_statistics, deweloperuch_rank_locations, deweloperuch_get_building) — what flats actually sold for, from the Real Estate Price Register. deweloperuch.pl is a free community project queried politely (one request at a time, results cached): if a result is an error starting with STOP, stop using the deweloperuch_* tools, retry nothing, look for no workaround and tell the user that market data is temporarily unavailable. Fields ending in _url are pages of deweloperuch.pl: give them to the user as links. Result shape: { total: number | null (null when the site does not say — a search by name), returned, truncated, hint?, source, items: [with city: { investment_slug, name, city_slug?, district?, street?, status? ('active' | 'archived'), offers_active?, offers_total?, avg_price?, avg_area_m2?, avg_price_per_m2? (active offers only, as the site counts them), developer_slug?, developer_name?, investment_url?, developer_url? } | by name: { investment_slug, name, offers_active? }] } — the list key is items.

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": "deweloperuch_search_investments"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNocity_slug of one city from deweloperuch_search_locations, e.g. warszawa, sopot (not polska).
nameNoFragment of an investment name, 2–100 characters, e.g. Kolibki. With city, case and Polish characters do not matter; without city the site searches the whole country.
sortNoOnly with city. active_offers (default): most active offers; price_per_m2_asc / price_per_m2_desc: average price per m²; price_asc / price_desc: average price; name: alphabetical. Entries without an average come last.
limitNoMost investments in the result, 1–30, default 10 (about 550–750 characters each with links).
developer_slugNodeveloper_slug from deweloperuch_search_developers or from results of the investment tools, e.g. atal. Only with city.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this as a read-only, open-world tool, and the description adds substantial operational context beyond them: polite one-request-at-a-time querying, caching, STOP-error handling, and what happens when market data is temporarily unavailable. It also explains the result shape, truncation fields, and sort behavior for entries lacking averages.

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?

The definition is front-loaded with purpose, modes, and usage, and most of its length is justified by the tool's complexity and the need to prevent mixing asking prices with RCN transaction prices. It is dense and somewhat repetitive in places, but the structure remains navigable and no major section is wasted.

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?

Given the five parameters, multiple search modes, absence of an output schema, and the risk of confusing this tool with pricing/transaction siblings, the description is complete. It covers return shape, field meanings, mode-dependent behavior, error handling, and cross-tool boundaries.

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%, so the baseline is 3; the schema already documents city, name, sort, limit, and developer_slug in detail. The description reinforces the city-versus-name-only distinction and notes that name and developer_slug narrow the list, but it does not add much parameter-specific detail beyond what the schema already provides.

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 states a specific verb and resource ('Search investments (developer projects, primary market)') and immediately defines two modes: city search with full data versus name-only search across Poland. It clearly distinguishes this from siblings such as deweloperuch_get_investment and deweloperuch_get_offer.

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

Usage Guidelines5/5

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

It gives explicit when-to-use examples (cheapest per m² in a city, investments of one developer, finding a slug by name) and names alternatives for excluded cases: offer details go to deweloperuch_get_investment, price history to deweloperuch_get_offer, and price/area ranges to deweloperuch_get_market_statistics. It also warns that city=polska does not work.

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