BRONLA

Search Rentals

search_rentals

Read-only

Bronla.UZ'dan dachalarni sanalari va mehmonlar soni bo'yicha qidiradi.

check_in / check_out: `YYYY-MM-DD` yoki `dd-mm-yyyy` (masalan 2026-06-19).
sort: 0=tavsiya, 1=arzon, 2=qimmat, 3=reyting.
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.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Natijalar sahifasi, 1-100.
`sort`	No	Saralash: 0=tavsiya, 1=arzon, 2=qimmat, 3=reyting.
`query`	No	Nom bo'yicha erkin qidiruv matni.
`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.
`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.

Output Schema

TableJSON 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, score, image, url va boshqalar.
`currency`	No	Narxlar valyutasi (UZS).
`countPage`	No	Sahifalar umumiy soni.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4/5.0

Behavior4/5

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

With annotations covering read-only and open-world access, the description adds valuable behavioral details: the compact return fields, max_images behavior, and the critical rule that providing only one date silently ignores the filter and triggers an error asking for both dates.

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 description is well-structured and front-loaded with purpose, then parameter details, return format, and a key constraint. Some parameter format details duplicate the schema, but every sentence largely earns its place.

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?

Given 12 parameters, an output schema, and annotations, the description is largely complete for correct invocation. It covers the critical date-pairing behavior and return shape, though it omits explicit guidance against sibling tools like search_hotels or check_availability.

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 description coverage is 100%, so the baseline is 3, but the description adds meaningful constraints beyond the schema: check_in/check_out must be supplied together, the error behavior when only one is given, and the sort mapping and max_images range.

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 description states a specific verb and resource: searching dachas/rentals from Bronla.UZ by dates and guests. It distinguishes from get_listing_details by saying each listing need not be opened separately, but does not explicitly differentiate from search_hotels or check_availability.

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

Usage Guidelines4/5

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

It gives a clear alternative (use this result instead of opening each listing with get_listing_details) and explains the important when-not/error condition for check_in/check_out. It does not explicitly state when to use this versus search_hotels or check_availability.

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?