BinaSmart

Hotel rooms and prices

get_hotel_rooms

Read-only

Room types, nightly prices (ETB), capacity and amenities for a hotel listed on BinaSmart. Use the slug from search_places (is_hotel = true).

Input Schema

Name	Required	Description	Default
`slug`	Yes	Hotel slug from search_places

Output Schema

Name	Required	Description
`demo`	No	true for a demo listing
`hotel`	No	Hotel
`rooms`	No	Room types
`book_url`	No	Booking page
`source_url`	No	bina.et page this result comes from; cite it
`demo_notice`	No	Shown when the listing is a demo

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "book_url": {
+      "description": "Booking page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "demo": {
+      "description": "true for a demo listing",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "demo_notice": {
+      "description": "Shown when the listing is a demo",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hotel": {
+      "anyOf": [
+        {
+          "additionalProperties": true,
+          "properties": {
+            "city": {
+              "description": "City",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name": {
+              "description": "Name",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "name_am": {
+              "description": "Name in Amharic",
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "sub_city": {
+              "description": "Sub-city",
+              "type": [
+                "string",
+                "null"
+              ]
+            }
+          },
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Hotel"
+    },
+    "rooms": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "capacity": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Guests"
+              },
+              "name": {
+                "description": "Room type",
+                "type": [
+                  "string",
+                  "null"
+                ]
+              },
+              "price_per_night_etb": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Nightly price in birr"
+              },
+              "total_rooms": {
+                "anyOf": [
+                  {
+                    "type": [
+                      "number",
+                      "string"
+                    ]
+                  },
+                  {
+                    "type": "null"
+                  }
+                ],
+                "description": "Rooms of this type"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Room types"
+    },
+    "source_url": {
+      "description": "bina.et page this result comes from; cite it",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that prices are in ETB, but says nothing about freshness of pricing, availability guarantees, or pagination behavior.

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

Conciseness5/5

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

Two compact sentences with zero filler; the returned fields lead and the prerequisite follows. Nothing is padded or restated.

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?

An output schema exists, so return values need not be detailed, and the one required parameter plus its source are covered. The definition is sufficient to invoke the tool correctly, with only minor gaps around pricing freshness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single slug parameter is already documented as coming from search_places, so the schema carries the load. The description's only marginal addition is the is_hotel = true filter hint for choosing the right slug, which is a minor but real clarification.

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 names the resource (room types, prices, capacity, amenities for a hotel) and implicitly the retrieval action, so an agent knows exactly what data comes back. It also ties itself to the slug-based lookup pattern, though it does not explicitly contrast with the sibling search_hotels/search_places tools beyond sourcing the slug.

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 concrete prerequisite chain: obtain the slug from search_places and only use results where is_hotel = true. That is clear actionable context, but there is no explicit when-not-to-use or mention of alternative hotel tools such as search_hotels.

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

All BinaSmart 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.