BRONLA

Get Listing Details

get_listing_details

Read-only

Bitta dacha/mehmonxonaning to'liq ma'lumotini va rasmlarini qaytaradi.

listing_slug - qidiruv natijasidagi `slug` maydoni. listing_type `house`
(dacha) yoki `property` (mehmonxona). Mehmonxonadagi bo'sh xonalarni
`check_hotel_availability` orqali tekshiring.
Tarkibida: tavsif, manzil/xarita, sig'im, qulayliklar, reyting, narx
(`payment`/`paydaylist`), oldindan to'lov foizi, band kunlar (`blocked_dates`)
va onlayn bron imkoniyati.

Eslatma: detail endpoint'da tayyor `price` YO'Q - narx `payment` ro'yxatida
(sig'im bo'yicha ish kunlari/hafta oxiri) va `paydaylist` (sana bo'yicha)
keladi. Aniq bo'sh kunlarni `check_availability` orqali so'rang.

Rasmlar: 10 tagacha rasm natijaga rasm (image content) sifatida qo'shiladi;
ularning URL'lari `images` ro'yxatida. Faqat matn kerak bo'lsa (narx, bo'sh
kunlar) - `max_images=0` yuboring.

Bir nechta dachani rasmlari bilan solishtirish uchun bu tool'ni har biriga
alohida chaqirmang: `search_rentals`/`search_hotels` natijasida har bir
e'lonning rasmi allaqachon bor. Bu tool - bitta e'lonni batafsil ko'rish uchun.

Joylashuv: `address` - egasining qisqa mo'ljali; "qayerda?" savoliga
`location_summary` va `map_url` bilan javob bering.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listing_slug": "<listing_slug>"
    },
    "name": "get_listing_details"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Javob tili: uz, ru yoki en - foydalanuvchi yozgan tilni bering. Hudud nomlari va tavsif tarjimasi shu tilda keladi.
`max_images`	No	Natijaga biriktiriladigan rasmlar soni, 0-10 (0 = rasmsiz).
`listing_slug`	Yes	Qidiruv natijasidagi e'lon `slug` qiymati.
`listing_type`	No	`house` (dacha) yoki `property` (mehmonxona).	house

Output Schema

Name	Required	Description
`id`	No	E'lon ID'si (create_booking.listing_id).
`url`	No	Saytdagi e'lon sahifasi.
`hint`	No	Xatoni qanday tuzatish haqida ko'rsatma.
`name`	No	E'lon nomi.
`slug`	No	E'lon slug'i.
`about`	No	Tavsif: `original` (egasi yozgan tilda) va `translated` (so'ralgan `lang` tilida).
`error`	No	Xato kodi; faqat tool bajarilmaganda keladi.
`found`	No	E'lon topildimi.
`detail`	No	Upstream API xatosi tafsiloti.
`images`	No	Rasm URL'lari (10 tagacha).
`address`	No	Egasi yozgan mo'ljal (ko'pincha qisqa/norasmiy). Joylashuv uchun `location_summary` va `map_url` dan foydalaning.
`map_url`	No	Koordinatalar bo'yicha Google Maps havolasi.
`payment`	No	Sig'im bo'yicha ish kuni / hafta oxiri narxlari.
`currency`	No	Narxlar valyutasi (UZS).
`paydaylist`	No	Sana bo'yicha narxlar.
`blocked_dates`	No	Band kunlar (60 tagacha).
`onlinebooking`	No	Onlayn bron yoqilganmi.
`recent_reviews`	No	Oxirgi 5 ta mehmon sharhi: author, rating (1-10), date, text (asl tilda).
`location_summary`	No	Hudud va mamlakat, masalan `Chorvoq, O'zbekiston`.
`blocked_dates_total`	No	Band kunlar umumiy soni.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 7, 2026

addedOutput schema / properties / recent_reviews

Added value: +{
+  "description": "Oxirgi 5 ta mehmon sharhi: author, rating (1-10), date, text (asl tilda).",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "title": "Recent Reviews",
+  "type": "array"
+}

Changed5 schema fields changedOct 7, 2026

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"
+}

addedOutput schema / properties / about

Added value: +{
+  "description": "Tavsif: `original` (egasi yozgan tilda) va `translated` (so'ralgan `lang` tilida).",
+  "title": "About"
+}

addedOutput schema / properties / address

Added value: +{
+  "description": "Egasi yozgan mo'ljal (ko'pincha qisqa/norasmiy). Joylashuv uchun `location_summary` va `map_url` dan foydalaning.",
+  "title": "Address",
+  "type": "string"
+}

addedOutput schema / properties / location_summary

Added value: +{
+  "description": "Hudud va mamlakat, masalan `Chorvoq, O'zbekiston`.",
+  "title": "Location Summary",
+  "type": "string"
+}

addedOutput schema / properties / map_url

Added value: +{
+  "description": "Koordinatalar bo'yicha Google Maps havolasi.",
+  "title": "Map Url",
+  "type": "string"
+}

Changed4 schema fields changedOct 6, 2026

addedInput schema / properties / listing_slug / description

Added value: +"Qidiruv natijasidagi e'lon `slug` qiymati."

addedInput schema / properties / listing_type / description

Added value: +"`house` (dacha) yoki `property` (mehmonxona)."

addedInput schema / properties / max_images / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "blocked_dates": {
+      "description": "Band kunlar (60 tagacha).",
+      "items": {},
+      "title": "Blocked Dates",
+      "type": "array"
+    },
+    "blocked_dates_total": {
+      "description": "Band kunlar umumiy soni.",
+      "title": "Blocked Dates Total",
+      "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"
+    },
+    "found": {
+      "description": "E'lon topildimi.",
+      "title": "Found",
+      "type": "boolean"
+    },
+    "hint": {
+      "description": "Xatoni qanday tuzatish haqida ko'rsatma.",
+      "title": "Hint"
+    },
+    "id": {
+      "anyOf": [
+        {
+          "type": "integer"
+        },
+        {
+          "type": "string"
+        }
+      ],
+      "description": "E'lon ID'si (create_booking.listing_id).",
+      "title": "Id"
+    },
+    "images": {
+      "description": "Rasm URL'lari (10 tagacha).",
+      "items": {
+        "type": "string"
+      },
+      "title": "Images",
+      "type": "array"
+    },
+    "name": {
+      "description": "E'lon nomi.",
+      "title": "Name",
+      "type": "string"
+    },
+    "onlinebooking": {
+      "description": "Onlayn bron yoqilganmi.",
+      "title": "Onlinebooking",
+      "type": "boolean"
+    },
+    "paydaylist": {
+      "description": "Sana bo'yicha narxlar.",
+      "title": "Paydaylist"
+    },
+    "payment": {
+      "description": "Sig'im bo'yicha ish kuni / hafta oxiri narxlari.",
+      "title": "Payment"
+    },
+    "slug": {
+      "description": "E'lon slug'i.",
+      "title": "Slug",
+      "type": "string"
+    },
+    "url": {
+      "description": "Saytdagi e'lon sahifasi.",
+      "title": "Url",
+      "type": "string"
+    }
+  },
+  "title": "ListingDetails",
+  "type": "object"
+}

First observedOct 6, 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=true and openWorldHint=true, so safety is covered. The description adds genuinely non-obvious behavior: up to 10 images are attached as image content with URLs in `images`, and there is no ready `price` field — price lives in `payment`/`paydaylist` broken down by capacity and weekend. This is real behavioral context beyond the 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 is front-loaded and the paragraphing groups purpose, price caveat, image behavior, and location handling logically. It is on the long side for a single-listing getter, but nearly every sentence carries actionable routing or output semantics rather than 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?

Given an output schema exists, return values need little explanation, yet the description still covers contents, image attachment behavior, price-source caveat, and location answering strategy. An agent can call this correctly and interpret results without opening the schema.

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 parameters are already documented and the baseline is 3. The description adds usable semantics on top: max_images=0 meaningfully signals a text-only mode, and it ties listing_slug to the `slug` field of search results, plus explains the house/property mapping. Only mildly redundant with the schema.

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?

The opening states a specific verb and resource: it returns full information and images for a single dacha/hotel listing. It clearly delineates itself from siblings, explicitly noting it is for viewing one listing in detail rather than being called per-listing for comparison against search_rentals/search_hotels.

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?

Explicitly routes the agent: empty hotel rooms go to check_hotel_availability, exact free dates to check_availability, and bulk image comparison to search_rentals/search_hotels instead of repeated calls. It also states when to send max_images=0 for text-only needs.

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?