BRONLA

Search Rentals

search_rentals

Read-only

Bronla.UZ'dan dachalarni hudud, qulayliklar, sana va mehmonlar soni bo'yicha qidiradi.

province: hudud nomi ("Chorvoq", "Чарвак") yoki ID - "Chorvoqda dacha"
so'rovida hududni `query` ga emas, shu yerga bering.
amenities: ["sauna", "pool"] - barchasi bor dachalar qaytadi.
check_in / check_out: `YYYY-MM-DD` yoki `dd-mm-yyyy` (masalan 2026-06-19).
sort: 0=tavsiya, 1=arzon, 2=qimmat, 3=reyting (sharhsiz e'lonlar oxirida).
"Eng yaxshisini tavsiya qil" uchun sort=3 va `countReview` ga qarang.
Natijada ixcham ro'yxat qaytadi: nomi, narxi, reytingi va havolasi.
max_images: birinchi nechta natijaning rasmi biriktirilsin (standart 6, 0-10).
Variantlarni rasmlari bilan ko'rsatish uchun shu natijadan foydalaning -
har bir e'lonni `get_listing_details` bilan alohida ochish shart emas.

check_in / check_out ixtiyoriy, lekin ikkalasi BIRGA berilishi kerak:
bittasi bersa API sana filtrini jimjiyoq e'tiborga olib, filtrlanmagan
natija qaytaradi. Bunday holatda xato qaytarilib, modeldan ikkala sana
so'raladi.

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

Input Schema

Name	Required	Description
`lang`	No	Javob tili: uz, ru yoki en - foydalanuvchi yozgan tilni bering. Hudud nomlari va tavsif tarjimasi shu tilda keladi.
`page`	No	Natijalar sahifasi, 1-100.
`sort`	No	Saralash: 0=tavsiya, 1=arzon, 2=qimmat, 3=reyting.
`query`	No	E'lon nomi bo'yicha erkin qidiruv. Hudud uchun `province` parametrini ishlating.
`rooms`	No	Minimal xonalar soni.
`adults`	No	Kattalar soni.
`check_in`	No	Kirish sanasi: YYYY-MM-DD yoki dd-mm-yyyy. check_out bilan birga beriladi.
`children`	No	Bolalar soni.
`price_to`	No	Maksimal narx, UZS.
`province`	No	Hudud: viloyat, tuman/shahar yoki joy (qishloq, dam olish zonasi) nomi, slug'i yoki ID'si - masalan `Chorvoq`, `Bo'stonliq`, `Toshkent viloyati`, `Чарвак`, `2`. Bir nechtasi `\|` bilan: `Chorvoq\|Qibray`. Ro'yxat: `list_search_filters` (`locations`).
`amenities`	No	Qulayliklar (BARCHASI bo'lishi shart): nomi yoki ID'si, o'zbek/rus/ingliz tilida - masalan ["sauna", "pool"], ["Finskaya sauna", "Jakuzi"]. Maxsus: pool (ochiq yoki yopiq basseyn), outdoor_pool, indoor_pool, waterfront, pets, alcohol, landscape. Ro'yxat: `list_search_filters`.
`check_out`	No	Chiqish sanasi: YYYY-MM-DD yoki dd-mm-yyyy. check_in bilan birga beriladi.
`max_images`	No	Natijaga biriktiriladigan rasmlar soni, 0-10 (0 = rasmsiz).
`price_from`	No	Minimal narx, UZS.
`province_id`	No	Viloyat/hudud ID'si bo'yicha filtr (eski nom; `province` bilan bir xil, nom ham qabul qilinadi).

Output Schema

Name	Required	Description
`hint`	No	Xatoni qanday tuzatish haqida ko'rsatma.
`page`	No	Joriy sahifa raqami.
`count`	No	Topilgan e'lonlar umumiy soni.
`error`	No	Xato kodi; faqat tool bajarilmaganda keladi.
`detail`	No	Upstream API xatosi tafsiloti.
`results`	No	E'lonlar: id, slug, name, province, price (matn), price_value (son, UZS), score, countReview, image, url va boshqalar.
`currency`	No	Narxlar valyutasi (UZS).
`countPage`	No	Sahifalar umumiy soni.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 21, 2026

changedInput schema / properties / province / description

Previous value: -"Hudud: nomi, slug'i yoki ID'si - masalan `Chorvoq`, `bostonliq`, `Чарвак`, `2`. Bir nechtasi `|` bilan: `Chorvoq|Bochka`. Ro'yxat: `list_search_filters`."New value: +"Hudud: viloyat, tuman/shahar yoki joy (qishloq, dam olish zonasi) nomi, slug'i yoki ID'si - masalan `Chorvoq`, `Bo'stonliq`, `Toshkent viloyati`, `Чарвак`, `2`. Bir nechtasi `|` bilan: `Chorvoq|Qibray`. Ro'yxat: `list_search_filters` (`locations`)."

Changed6 schema fields changedOct 7, 2026

addedInput schema / properties / amenities

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Qulayliklar (BARCHASI bo'lishi shart): nomi yoki ID'si, o'zbek/rus/ingliz tilida - masalan [\"sauna\", \"pool\"], [\"Finskaya sauna\", \"Jakuzi\"]. Maxsus: pool (ochiq yoki yopiq basseyn), outdoor_pool, indoor_pool, waterfront, pets, alcohol, landscape. Ro'yxat: `list_search_filters`.",
+  "title": "Amenities"
+}

addedInput schema / properties / lang

Added value: +{
+  "anyOf": [
+    {
+      "enum": [
+        "uz",
+        "ru",
+        "en"
+      ],
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Javob tili: uz, ru yoki en - foydalanuvchi yozgan tilni bering. Hudud nomlari va tavsif tarjimasi shu tilda keladi.",
+  "title": "Lang"
+}

addedInput schema / properties / province

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Hudud: nomi, slug'i yoki ID'si - masalan `Chorvoq`, `bostonliq`, `Чарвак`, `2`. Bir nechtasi `|` bilan: `Chorvoq|Bochka`. Ro'yxat: `list_search_filters`.",
+  "title": "Province"
+}

changedInput schema / properties / province_id / description

Previous value: -"Viloyat/hudud ID'si bo'yicha filtr."New value: +"Viloyat/hudud ID'si bo'yicha filtr (eski nom; `province` bilan bir xil, nom ham qabul qilinadi)."

changedInput schema / properties / query / description

Previous value: -"Nom bo'yicha erkin qidiruv matni."New value: +"E'lon nomi bo'yicha erkin qidiruv. Hudud uchun `province` parametrini ishlating."

changedOutput schema / properties / results / description

Previous value: -"E'lonlar: id, slug, name, province, price, score, image, url va boshqalar."New value: +"E'lonlar: id, slug, name, province, price (matn), price_value (son, UZS), score, countReview, image, url va boshqalar."

Changed13 schema fields changedOct 6, 2026

addedInput schema / properties / adults / description
```
Added value: +"Kattalar soni."
```

addedInput schema / properties / check_in / description

Added value: +"Kirish sanasi: YYYY-MM-DD yoki dd-mm-yyyy. check_out bilan birga beriladi."

addedInput schema / properties / check_out / description

Added value: +"Chiqish sanasi: YYYY-MM-DD yoki dd-mm-yyyy. check_in bilan birga beriladi."

addedInput schema / properties / children / description
```
Added value: +"Bolalar soni."
```

addedInput schema / properties / max_images / description

Added value: +"Natijaga biriktiriladigan rasmlar soni, 0-10 (0 = rasmsiz)."

addedInput schema / properties / page / description
```
Added value: +"Natijalar sahifasi, 1-100."
```
addedInput schema / properties / price_from / description
```
Added value: +"Minimal narx, UZS."
```
addedInput schema / properties / price_to / description
```
Added value: +"Maksimal narx, UZS."
```
addedInput schema / properties / province_id / description
```
Added value: +"Viloyat/hudud ID'si bo'yicha filtr."
```

addedInput schema / properties / query / description

Added value: +"Nom bo'yicha erkin qidiruv matni."

addedInput schema / properties / rooms / description
```
Added value: +"Minimal xonalar soni."
```

addedInput schema / properties / sort / description

Added value: +"Saralash: 0=tavsiya, 1=arzon, 2=qimmat, 3=reyting."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "description": "Topilgan e'lonlar umumiy soni.",
+      "title": "Count",
+      "type": "integer"
+    },
+    "countPage": {
+      "description": "Sahifalar umumiy soni.",
+      "title": "Countpage",
+      "type": "integer"
+    },
+    "currency": {
+      "description": "Narxlar valyutasi (UZS).",
+      "title": "Currency",
+      "type": "string"
+    },
+    "detail": {
+      "description": "Upstream API xatosi tafsiloti.",
+      "title": "Detail"
+    },
+    "error": {
+      "description": "Xato kodi; faqat tool bajarilmaganda keladi.",
+      "title": "Error"
+    },
+    "hint": {
+      "description": "Xatoni qanday tuzatish haqida ko'rsatma.",
+      "title": "Hint"
+    },
+    "page": {
+      "description": "Joriy sahifa raqami.",
+      "title": "Page",
+      "type": "integer"
+    },
+    "results": {
+      "description": "E'lonlar: id, slug, name, province, price, score, image, url va boshqalar.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "title": "Results",
+      "type": "array"
+    }
+  },
+  "title": "SearchResult",
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral detail beyond that: half-supplied dates are silently ignored by the API and an error is raised asking for both dates, amenities use AND semantics, and sort ordering places unrated listings last. It does not discuss rate limits or pagination, hence not a 5.

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?

It is front-loaded with the purpose and then organized as parameter-prefixed lines, so an agent can scan it quickly. A few lines (the `sort` code list, the `amenities` example) largely restate schema text, which is minor redundancy rather than filler.

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 15 parameters, an output schema, and full schema coverage, the description covers the parameters that drive real agent decisions (province, dates, amenities, sort, max_images) and the cross-tool workflow. The leaf parameters (rooms, adults, children, price bounds, lang, page) are left entirely to the schema, which is acceptable given its 100% coverage.

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 3 is the baseline, but the description adds meaning the schema does not: the date-pairing failure mode, the `province` vs `query` split, `sort` tie-break behavior with `countReview`, and the fact that `max_images` controls image attachment on the first N results. That is meaningful added semantics above the schema's own text.

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 opening sentence gives a specific verb, resource and scope ('Bronla.UZ'dan dachalarni ... qidiradi') and enumerates the filter dimensions (region, amenities, dates, guests). The dacha/villa resource clearly separates it from the hotel siblings, though it never names `search_hotels` explicitly, so the distinction is inferential rather than stated.

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 concrete routing rules: region names must go to `province`, not `query`; use `sort=3` plus `countReview` for 'recommend the best'; use this tool's embedded images instead of opening each listing with `get_listing_details`. It also states the when-not condition for dates (both or neither), which is exactly the kind of exclusion guidance that prevents misuse.

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

All BRONLA tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?