Skip to main content
Glama

Gratka MCP

Search Polish real-estate listings (Gratka.pl)

gratka_search

Search property listings on Gratka.pl, a major Polish real-estate portal: flats, houses, plots, commercial premises, offices, garages and rooms, for sale or for rent, filtered by location (any Polish city, district, town, village, county or voivodeship), price, area, rooms, private sellers only and primary/secondary market, sorted like the site. Returns one results page (up to 35 listings) with each listing's price, price per m², area, rooms, floor, location, seller and link; pass a listing id to gratka_offer for the full details. Gratka.pl shows the same listings as Morizon.pl (one platform, different ids and links): search one portal, not both, and use gratka_offer only with Gratka.pl ids. Fetched live from Gratka.pl's own API (typically under 1 s). Result shape: { source, fetchedAt, query, search_url, heading, resolved_location, total_count, page, total_pages, count, listings: [...], note? } — the list key is listings; total_count counts matches across all pages (use page for more); resolved_location is the place location was matched to. Each listing: { source, id, url, title, category, kind, development, price, price_per_m2, currency, area_m2, rooms, floor, location, street, district, city, region, seller_type, seller_name, date_posted, refreshed_at, image, photo_count, description }. Prices are numbers in PLN (for rent, price is the monthly rent) and area is in m²; fields are null when the listing omits them. kind is 'new_development' for a developer's unit in a new project (named in development), else 'listing'; seller_type is agency | private | developer. An empty match answers count: 0 with a note saying why and what to change — that is a successful result, not an error.

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, 1-based (35 listings per page). Default 1.
sortNoOrder: 'newest' (recently added), 'price_asc' / 'price_desc', 'price_per_m2_asc' / 'price_per_m2_desc', 'area_asc' / 'area_desc'. Default: the site's own order (recently refreshed).
typeYesProperty type: 'flat' = mieszkanie, 'house' = dom, 'plot' = działka/grunt (land), 'commercial' = lokal użytkowy (any commercial premises), 'office' = biuro, 'garage' = garaż, 'room' = pokój (a room to rent — rent only).
marketNo'primary' = new build from a developer (rynek pierwotny), 'secondary' = resale (rynek wtórny).
area_maxNoMaximum area in m² (the plot's area for type 'plot').
area_minNoMinimum area in m² (the plot's area for type 'plot').
locationNoWhere, as a Polish place name, matched by the site's own location search: a city ('Kraków'), a district ('Warszawa Mokotów', 'Gdańsk Wrzeszcz'), a town or village, a county ('krakowski') or a whole voivodeship ('mazowieckie'). Diacritics are optional; English names other than Warsaw/Cracow are not recognised. Omit to search all of Poland.
no_cacheNoForce a fresh fetch and bypass this server's result cache (5 min). Default false.
price_maxNoMaximum total price in PLN (monthly rent when transaction is 'rent').
price_minNoMinimum total price in PLN (monthly rent when transaction is 'rent').
rooms_maxNoMaximum number of rooms — not for types 'plot' and 'garage' (use min = max for exactly N).
rooms_minNoMinimum number of rooms — not for types 'plot' and 'garage'.
transactionYes'sale' = na sprzedaż (buying), 'rent' = na wynajem (renting; prices are monthly).
private_onlyNoOnly listings posted by private owners — no agencies or developers. Default false.

Output Schema

NameRequiredDescriptionDefault
noteNo
pageYes
countYes
queryYes
sourceYes
headingNo
listingsYes
fetchedAtYes
search_urlYes
total_countNo
total_pagesNo
resolved_locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so: live fetch from Gratka.pl's own API with typical sub-second latency, a 5-minute server cache, one results page of up to 35 listings, null-valued fields when omitted, price in PLN (monthly for rent), and area in m². It also discloses the meaning of `kind`, `seller_type`, `total_count` versus `page`, and what `resolved_location` represents.

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 purpose and routing before the long result-shape block, and every clause is informational. It is on the long side, with the listing field list appearing both in the shape summary and again in a per-field enumeration that partly duplicates the existing output schema.

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 14-parameter, annotation-free search tool this covers everything an agent needs: what is searched, how to route elsewhere, page size and pagination, units, caching, empty-result handling, and field semantics. The return-value detail is technically redundant with the output schema but adds interpretive value rather than noise.

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; the description goes beyond it by tying units and interpretation to transaction type ('prices are numbers in PLN, for rent `price` is the monthly rent'), clarifying that prices/areas are numeric, and explaining that `location` is resolved by the site's own matcher and surfaces as `resolved_location`. It does not, however, restate the enum semantics for `type`, `sort` or `market`, which the schema already handles.

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 ('Search property listings on Gratka.pl'), enumerates the property types and transaction modes covered, and names the sibling it hands off to (gratka_offer) as well as the portal it deliberately duplicates (Morizon.pl). An agent can distinguish it from morizon_search and gratka_offer without opening a schema.

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 explicit routing: pass a listing `id` to gratka_offer for full details, use gratka_offer only with Gratka.pl ids, and 'search one portal, not both' because Gratka.pl and Morizon.pl expose identical inventory. It also states that an empty match is a successful result rather than an error, which prevents a common misreaction.

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