deweloperuch-mcp

Profil dewelopera

get_developer

Read-only

Retrieve a Polish developer's profile: active offers, investments, cities, average prices and URLs to see where and at what prices they build.

Instructions

Zwraca profil dewelopera: nazwę, stronę www, podsumowanie jego aktywnych ofert (summary: active_offers, cities, avg_price, avg_area_m2, avg_price_per_m2), inwestycje z aktywnymi ofertami (najpierw te z największą liczbą aktywnych ofert: investment_slug, name, city, active_offers, total_offers razem z archiwalnymi, średnie aktywnych ofert, investment_url) i jego miasta (cities: inwestycje, aktywne oferty, średnia cena i cena za m²). Użyj, gdy pytanie dotyczy dewelopera: gdzie i ile buduje, w jakich cenach. developer_slug weź z search_developers (po nazwie) albo z pól developer_slug w search_offers, get_investment, get_offer. developer_url i investment_url to strony na deweloperuch.pl: podawaj je użytkownikowi jako linki.

city zawęża summary i investments do jednego miasta (city_slug z search_locations); domyślnie polska (cała Polska). cities zawsze obejmuje całą Polskę.

Ograniczenia: najwyżej limit inwestycji (domyślnie 20); investments_omitted i truncated mówią, ile pominięto. Pojedynczych ofert tu nie ma: oferty inwestycji daje get_investment.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No	city_slug miasta z search_locations (np. krakow) albo polska (domyślnie: cała Polska).	polska
`limit`	No	Najwięcej inwestycji w wyniku (najpierw te z największą liczbą aktywnych ofert), 1–100, domyślnie 20. Inwestycja to ok. 350 znaków wyniku; zwykle wystarcza domyślne 20.
`developer_slug`	Yes	developer_slug z search_developers (po nazwie) albo z pól developer_slug w search_offers, get_investment, get_offer, np. atal.

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No
`cities`	Yes	Wszystkie miasta dewelopera w Polsce, niezależnie od argumentu city (także przy city=warszawa).
`summary`	Yes
`city_slug`	Yes	Zakres summary i investments: miasto albo polska.
`developer`	Yes
`truncated`	Yes	true: lista investments jest niepełna.
`investments`	Yes
`developer_url`	No	Profil dewelopera na deweloperuch.pl: podaj go użytkownikowi jako link.
`investments_total`	Yes	Wszystkie inwestycje z aktywnymi ofertami.
`investments_omitted`	Yes	Inwestycji pominiętych przez limit.
`investments_returned`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Oct 16, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds non-obvious semantics: city narrows summary and investments while cities always covers all of Poland, and truncation is disclosed via investments_omitted and truncated. It also instructs that developer_url/investment_url should be surfaced to the user, which is an output-handling behaviour not visible in annotations.

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?

Purpose and scope are front-loaded, then slug sourcing, then city/limit constraints, so the structure is sound. The long parenthetical enumerations of output fields are partly redundant with the output schema and inflate the text, but no paragraph is filler.

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?

For a read-only profile tool with an output schema, the description covers everything an agent needs: what sections return, how to obtain the required slug, how city and limit scope results, what truncation signals mean, and which sibling handles individual offers. Nothing required for correct invocation is missing.

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%, so the baseline is 3, but the description adds real meaning beyond the schema: the ordering rule for limit (investments with most active offers first) and the subtle asymmetry that city does not scope the cities block. These are semantic constraints the schema fields alone do not convey.

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?

Opens with a specific verb+resource ('Zwraca profil dewelopera') and enumerates the returned sections (summary, investments, cities) with their sub-fields, so the agent knows exactly what this tool produces. It is clearly separable from siblings like get_investment, which the description explicitly names as the place for individual offers.

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?

Gives an explicit trigger ('Użyj, gdy pytanie dotyczy dewelopera: gdzie i ile buduje, w jakich cenach') plus an exclusion ('Pojedynczych ofert tu nie ma: oferty inwestycji daje get_investment'). It also routes the agent to the right source for the required slug (search_developers, search_offers, get_investment, get_offer).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server