Skip to main content
Glama

Gratka MCP

Search Polish real-estate listings (Morizon.pl)

morizon_search

Search property listings on Morizon.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 morizon_offer for the full details. Morizon.pl shows the same listings as Gratka.pl (one platform, different ids and links): search one portal, not both, and use morizon_offer only with Morizon.pl ids. Fetched live from Morizon.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.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: live API fetch with typical latency, a 5-minute server-side cache (echoed in no_cache), null-field semantics, seller_type/kind enumerations, and empty-result behavior. It also explains pagination limits (35/page, total_count across pages).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and information-dense, but the long block enumerating every field of the result object and each listing is largely redundant with the output schema and adds bulk without adding decision-relevant guidance. The core routing advice is buried mid-paragraph rather than split out.

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?

Excellent coverage for a 14-parameter search tool: the agent knows what it will get back, how pagination works, how empty results appear, and how this tool relates to both siblings. No material gap remains.

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 schema already documents every parameter. The description adds modest extra meaning (rent prices are monthly, prices in PLN, area in m², sorts 'like the site') but largely restates the filter list already in the schema, so it stays close to the baseline.

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?

Specific verb+resource ('Search property listings on Morizon.pl') plus an enumerated set of property types, transactions and filters. It also explicitly distinguishes itself from siblings by telling the agent to search one portal only and to pair it with morizon_offer rather than gratka_search.

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?

Explicit routing: 'Morizon.pl shows the same listings as Gratka.pl ... search one portal, not both, and use morizon_offer only with Morizon.pl ids.' It also clarifies that count: 0 with a note is a success, not an error, so the agent knows not to retry or treat it as a failure.

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